we have some projects with the same configuration and when we move them from one project to another one, Jira decides that it is not needed to change the status. Is it possible to force this to go to an specific status?
In our case, a ticket can be created and move in a project and then needs to o to another project to the first state in the workflow, in all cases.
Any ideas? I have tried with a plugin but it requires the pro version
when moving an issue, jira is only asking you to assign the values that are not defined the same way in the target project. If the target project has the same workflow you won't be asked.
So you are going to have to do two steps, first move the issue and then transition it.
This could be (it shouldn't be hard) automated with a postfunction script or an automation if you have any of those plugins
Hi @fran garcia gomera ,
I don't see how can I use a postfunction in this case. If I move from project A to project B, the postfunction should be once the issue is in project B and where how can I say this happens only when I'm moving an issue from another project?
The plugins that we have required a pro version and so far it does not look like it does what I need.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events