Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-549

New trigger for "Issue moved to project" and new action for "Move issue between projects"

    • 0
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Allow the "Then" actions in Jira to move issues to other projects.

      I have multiple situations where the Jira Automation is able to detect instances where certain issues will be handled in other projects, but cannot move them there.

      ***

      Problem

      When an issue is moved between projects, the request type is lost and the request type can't be edited while moving the ticket. This causes problems with communication with customers.

      Suggested resolution

      Add the "Issue Moved" trigger and action in the automation rules.

      Workaround

            [AUTO-549] New trigger for "Issue moved to project" and new action for "Move issue between projects"

            This is a must have.  Any update on when it might be addressed?

            Kellie Noumi added a comment - This is a must have.  Any update on when it might be addressed?

            Hello?? Any status on this? Its really annoying and has been an issue since 2019!!!

            Jill Vieregge added a comment - Hello?? Any status on this? Its really annoying and has been an issue since 2019!!!

            The cloning workaround causes a lot of headache and problems. Having this feature is a must for all kinds of organizations.

            Mauricio Heberle added a comment - The cloning workaround causes a lot of headache and problems. Having this feature is a must for all kinds of organizations.

            This would be a great option to have! The workaround doesn't work for what my organization is trying to achieve. Fingers crossed this one finally gets enough traction to be seen 🤞🏾

            Adrian.Bonaparte added a comment - This would be a great option to have! The workaround doesn't work for what my organization is trying to achieve. Fingers crossed this one finally gets enough traction to be seen 🤞🏾

            Not being able to automate this on certain status transitions creates a hassle for our team. Cloning wouldn't work because we need the comment history, attachments, and links for context. We also want to redirect to new link via other one as many apps have Jira integration and stores Jira ticket link that cant be modified, so there if we want to move ticket its not possible.
             

             

            Himanshu Gupta added a comment - Not being able to automate this on certain status transitions creates a hassle for our team. Cloning wouldn't work because we need the comment history, attachments, and links for context. We also want to redirect to new link via other one as many apps have Jira integration and stores Jira ticket link that cant be modified, so there if we want to move ticket its not possible.    

            This behavior would be incredibly helpful to our organization!  Agree with other comments - the workaround is not a viable option for many of us.  Thank you!

            Corey Saksik added a comment - This behavior would be incredibly helpful to our organization!  Agree with other comments - the workaround is not a viable option for many of us.  Thank you!

            The workaround by cloning the issue deletes the linked issues and attachments which are extremely important so this feature would be very helpful.

            Adnan Cudic added a comment - The workaround by cloning the issue deletes the linked issues and attachments which are extremely important so this feature would be very helpful.

            Craig Cote added a comment -

            Definitely a must-have.  Empower the automations!

            Craig Cote added a comment - Definitely a must-have.  Empower the automations!

            I don't want the workaround. I need this added to automation.

            Chris.Sterba added a comment - I don't want the workaround. I need this added to automation.

            Adding my voice to the crowd. Not being able to automate this on certain status transitions creates a hassle for some of our team. Cloning wouldn't work because we need the comment history, attachments, and links for context.

            Jonas Falberg added a comment - Adding my voice to the crowd. Not being able to automate this on certain status transitions creates a hassle for some of our team. Cloning wouldn't work because we need the comment history, attachments, and links for context.

              Unassigned Unassigned
              5ee4c75a3669 Ert Dredge
              Votes:
              272 Vote for this issue
              Watchers:
              151 Start watching this issue

                Created:
                Updated: