Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90033

Workflow pull request triggers always record anonymous users when performing a transition

XMLWordPrintable

      Issue Summary

      When using GitHub app or Bitbucket integration along with workflow triggers, the workflow transitions are shown as performed by Anonymous users

      Steps to Reproduce

      1. Connect your project with the GitHub for Jira app. 
      2. Configure your workflow triggers so that PullRequestCreated or PullRequestMerged transition your issue accordingly.
      3. Create or merge a pull request.

      Expected Results

      The user account who has performed the changes in GitHub is mapped correctly to a user on the issue history.

      Actual Results

      The issue history for the transition states that it was performed by an anonymous user.

      This is despite confirming that with a smart commit using:

      [Issue-Key]#comment TestComment 

      the comments are created with the correct user name, so it is able to identify the user from the commit operations but not for the workflow triggers.

      Workaround

      Currently there is no known workaround for this behavior.

        1. Screenshot 2020-09-05 at 1.01.27 AM.png
          Screenshot 2020-09-05 at 1.01.27 AM.png
          47 kB
        2. Screenshot 2020-09-09 at 12.09.27 PM.png
          Screenshot 2020-09-09 at 12.09.27 PM.png
          328 kB
        3. Screenshot 2020-09-09 at 12.10.01 PM.png
          Screenshot 2020-09-09 at 12.10.01 PM.png
          118 kB
        4. Screenshot 2020-09-09 at 12.12.53 PM.png
          Screenshot 2020-09-09 at 12.12.53 PM.png
          50 kB
        5. Screenshot 2020-09-09 at 12.15.09 PM.png
          Screenshot 2020-09-09 at 12.15.09 PM.png
          114 kB

            [JRACLOUD-90033] Workflow pull request triggers always record anonymous users when performing a transition

            Karina added a comment -

            The bug in Pullrequest transitions was fixed in February. 

            The behaviour for branch transitions is expected and documented in https://support.atlassian.com/jira-cloud-administration/docs/configure-workflow-triggers. The trigger will still be executed by anonymous users for Bitbucket and Github. Customers raising tickets because they don't want triggers to be executed with anonymous users would be a feature request, not a bug. 

            "How triggers relate to other workflow operations/constraints

            When a transition is triggered automatically, it ignores any conditions, validators or permissions configured on the transition.

            However, post functions are still executed. You need to be careful that if your post function requires a user, that your transition will not be executed by an anonymous user (see user mapping section above)."

            Karina added a comment - The bug in Pullrequest transitions was fixed in February.  The behaviour for branch transitions is expected and documented in  https://support.atlassian.com/jira-cloud-administration/docs/configure-workflow-triggers.  The trigger will still be executed by anonymous users for Bitbucket and Github. Customers raising tickets because they don't want triggers to be executed with anonymous users would be a feature request, not a bug.  "How triggers relate to other workflow operations/constraints When a transition is triggered automatically, it ignores any conditions, validators or permissions configured on the transition. However, post functions are still executed. You need to be careful that if your post function requires a user, that your transition will not be executed by an anonymous user (see  user mapping section  above)."

              kmoraesdasilva Karina
              prawat@atlassian.com Prashant R (Inactive)
              Affected customers:
              23 This affects my team
              Watchers:
              27 Start watching this issue

                Created:
                Updated:
                Resolved: