Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-21114

The option "User who triggered the event" does not work for Branch created trigger in Jira automation

XMLWordPrintable

      Issue Summary

      When using the Branch created trigger in Jira automation, The option "User who triggered the event" does not work to set the branch creator as the assignee of the issue related to the branch.

      Steps to Reproduce

      1. Integrate both Jira and Bitbucket applications
      2. Create the following automation rule in one of your integrated projects:
      3. Navigate to any issue of the project and click to create a branch:

      Expected Results

      The issue is assigned with the user who created the branch

      Actual Results

      The issue is not assigned.

      Workaround

      None so far.

        1. Screen Shot 2020-12-28 at 14.43.13.png
          Screen Shot 2020-12-28 at 14.43.13.png
          148 kB
        2. Screen Shot 2020-12-28 at 14.48.54.png
          Screen Shot 2020-12-28 at 14.48.54.png
          167 kB

          Form Name

            [JSWCLOUD-21114] The option "User who triggered the event" does not work for Branch created trigger in Jira automation

            Navya Krishna Dubbala added a comment -

            Any expected timelines to address this issue ??

            Navya Krishna Dubbala added a comment - Any expected timelines to address this issue ??

            Dylan added a comment -

            Hi all,

            Thank you for raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.

            To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            Dylan added a comment - Hi all, Thank you for raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            Stacy Mower added a comment -

            Finding this to be an issue with my team also

            Stacy Mower added a comment - Finding this to be an issue with my team also

            diego.belay added a comment -

            Our team is affected by this bug too

            diego.belay added a comment - Our team is affected by this bug too

            Thies Uhlenbruch added a comment -

            Is there any workaround?

            Thies Uhlenbruch added a comment - Is there any workaround?

            Lee Johnson added a comment -

            We have automation to move the card, but then we need to manually set the assignee, which negates the benefit of the automation in the first place.  

            Hoping this gets a priority bump.

            Lee Johnson added a comment - We have automation to move the card, but then we need to manually set the assignee, which negates the benefit of the automation in the first place.   Hoping this gets a priority bump.

            Josh Williams added a comment -

            While I know that the old triggers will be deprecated soon, as a workaround we could still use them (since they are not yet deprecated), correct?

            Josh Williams added a comment - While I know that the old triggers will be deprecated soon, as a workaround we could still use them (since they are not yet deprecated), correct?

              Unassigned Unassigned
              pgoncalves Petter Gonçalves
              Affected customers:
              51 This affects my team
              Watchers:
              49 Start watching this issue

                Created:
                Updated:
                Resolved: