I'm using External System Import to import project & issues in JIRA from another issue tracker.
Issues in that system (import source) have different statuses and that is causing errors during import.
I've created separate workflow with all new statuses in it, but External System Import is assigning "jira" read-only workflow to each project created during import. Such behavior results in error for each issue, because new statuses are not present in "jira" workflow.
Is there any way to specify which workflow (or workflow scheme) to use for projects created during import?
As a workaround I've waited for project without issues to be created and then changed used workflow manually. After that import finished without errors.
There may be an add-on that can accomplish this task. This may be possioble with the Bob Swift CLI as it has methods to associate workflows and schemes, however, it's not clear whether this can be modified during an import.
I would also recommend creating a Suggestion on JAC. This will get the request in front of the developers and allow others to vote on the feature request so it can hopefully be added to JIRA in the future as a native function.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs