When user is logged-in to Phabricator using Jira adapter then through Jira's OAuth it's allowed to perform different actions (e.g. adding comments, transitioning issues) on behalf of associated Phabricator user.

In the company we have workflow, where new Differential revisions, that are created are associated with Jira issues (Jira issue key is put into dedicated field). Currently Phabricator using that issue key to add comments to the issue based on actions user makes to revision itself and that is good.

I propose to make this even more helpful:

• when revision is accepted, then execute TransitionA for that issue on Jira side automatically
• when revision is rejected, then execute TransitionB for that issue on Jira side automatically

For both cases provide comment that is usually added to issue as part of a transition.

Without this I need to approve/reject associated Jira task by hand after doing this on Differential side.