Move tickets from une project to other depending on custom field

[AgileHappyLearner]

I need that for a specific project, every time an issue is created, the content of a specific custom field is read and depending on its content the ticket is moved to another project. This custom field has a list of approximately 40 possible values, each one related to a different project. Is it possible to automate this movement?

[Bill Sheboy]

Hi @AgileHappyLearner 

Just to confirm, are you using Jira Data Center?

If so, what you describe is likely not possible with an automation rule for several reasons:

• First, moving an issue requires checking several things and guiding the person through the move. That is not possible with an automation rule as the rule cannot stop and ask questions to confirm any changes to type, fields, etc.  One would need to pre-determine every possible contingency to workaround any problems with the move, making the rule even longer.  (please see below)
• There is no REST API endpoint to perform a move for Jira Data Center, and thus there is no automation rule action either.  Here is the suggestion to add that endpoint: https://jira.atlassian.com/browse/JRASERVER-61359
• Without an endpoint, one could take a chance and try directly editing the project field with advanced edit and JSON, although I have never tried that with Data Center.  Even if it was possible, you describe having 40 possible projects and that would require at least 82 rule components, but the limit is 65.  The 82 would be: 1 for a trigger, 1 for an if / else block, and 40 x (1 condition + 1 edit action).
  • An even riskier workaround would be using a single, complicated conditional expression to attempt to determine the project value.  Again, I have no idea if this would work with Data Center with a direct edit of the project field.

It seems you are trying to create a dispatcher to assign issues to projects based on a request field value.  Perhaps discuss this need with your Jira Site Admin to learn what is possible to help.

Kind regards,
Bill

[Thorsten Letschert _Decadis AG_]

Hey @AgileHappyLearner ,

As stated by the others, this is not a trivial task.

If your "Data Center" flag is correct here and using a third-party app is an option for you, I'd suggest checking out Jira Workflow Toolbox and its Move issue post function, which lets you move issues between projects. Please let me know if you need a helping hand regarding the setup.

Regards,
Thorsten

P.S. I'm part of the team behind the app mentioned above.

[Izabela França]

Hello, @AgileHappyLearner !

Unfortunately, Jira Cloud doesn't currently support using automation to move issues. The workaround would be creating an automation to clone the issue in the destination project and delete the original one. Here is an Atlassian documentation showing the steps to configure such automation [LINK HERE].

For the context you described, yoou would have to change the trigger to "issue created".

[Aaron Williams]

Hey @AgileHappyLearner 

This is very possible, you would use "work item created" as the trigger and then a series of IF/Elses to go through all the possible outcomes, with an action to move the ticket in each. 

For example : When work item created > if custom field = "X" > then clone work item to "project X"

Else if custom field = "y" > clone work item to "project y" 

Then you need to either add another action resolve to close the original work item, or delete it. 

The only thing I would say, is that if you need to move the ticket as it is, you'd need the target project to have the same custom fields to ensure no data loss.

Thanks

Aaron. 

[AgileHappyLearner]

Thanks for your reply! But isn't it really possible to move them, just clone and close them? On the other hand, the field's list of values ​​is around 40 and can keep growing. Is there any other way to do this other than concatenating if, else if?