Please check out our guide on requesting features in Phabricator. Specifically, it's helpful for us to understand what problem you are having with Phabricator and then we can look at various solutions. Right now I don't have any clear idea on what problem duplicating Audit into Maniphest could solve.

https://secure.phabricator.com/book/phabcontrib/article/feature_requests/#describe-problems

@nick.udell I'm still not really understanding the problem. It sounds like you're just copying information from Audit to Maniphest but I don't see what problem duplicating the information solves. If I have a commit with a Raised Concern, it's on my dashboard to address and I have all pertinent information to assign a new review to resolve the issue.

@chad the issue is that subsequent commits (made to fix concerns raised) are not easily linked to the commit that raised concerns and are harder for auditors to view in context with the commit they had originally audited.

It sounds like you want T4026 then?

I think you can write a custom HeraldAdapter to do what you want in the meantime, trying to see if we've documented that somewhere yet.

Yes, T4026 would be perfect.

Yeah I don't know why you would want to duplicate Audit details to Maniphest. Do these commits have a single merge commit which could be audited instead?

@joshuaspence the issue for me is that the commits made to fix the failed audit naturally do not occur until after the audit has failed, and so can't be in the same commit.

While all revisions made to fix an audit could be put in the same merge commit, and that would ameliorate the problem, there would still be the issue that the commit that failed audit is not linked to the fixes made for it. There's no way of just seeing them all in the same page, in the context of "this was marked as broken, these are the attempts to fix it".

I end up with this situation: "I have raised concerns on this commit, how do I see what commits have been made to fix this? How can I verify that the issues from the audit are fixed and that there have not been new issues created in fixing the previous issues?"

The reason I am involving Maniphest here is that it allows me to link all the commits in one place, with the Maniphest task being the context of "A failed audit and all commits made to fix it." It is not necessarily ideal as, yes, it does duplicate data, but I cannot find a better solution currently.

Yeah, T4026 seems like a reasonable path forward here in that there would exist a relation for "commit X addressed concerns raised in commit Y".