As part of the migration, we are importing the projects from Cloud to server(hosted on AWS) instance. While we testing the tickets after import , observed that all imported tickets are assigned to same assignee, who are the automatic assignee in workflow post function.
I found below article from our Atlassian documentation, this make sense, but i didn't see any disable option in workflow post function. Could anyone please suggest me how to overcome this problem on production instance ? And as per the Atlassian guidelines, we have to create workflows manually on target instance instead of exporting and importing, but our worklfows are big and have lot of transitions to design.
"When importing a project, the Create Issue transition and the Issue Created event will be triggered for each issue along with all corresponding postfunction. If you change the Create Issue transition after the import (for example, setting one of the create issue field values), you may get values that are different from those in the source. As a workaround, you can manually disable postfunctions during the import. "
Just remove the auto assign rule for the issue created event. This might be in workflow or automation rule. Don't try to remove the event itself.
I have migrated thousands of issues but didn't use the Atlassian site import. We used csv import with our own scripts. Didn't run into this issue though.
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