Verify doesn't identify missing resolutions until the import is run proper. I found "No Work Planned" resolution was missing. But the verify option failed to spot this
Similarly after running a clean verify the load reported this error
An error occurred during the load:
Load failed for reason: Trying to associate permission scheme entity to project role with name: Managers that does not exist
Incidentally, this was caused by the fact that "Managers " role existed (note the trailing space)
Yes, it is the case that some errors go undetected by the verify/simulated load option and they show up when the actual import is executed. We have been improving this slowly in the plugin versions, and there will be a substantial progress in this area in the mid term (before end of the year). This would include detection of the two examples you mention here.
Nevertheless, bear in mind that detection of 100% of errors in the verify/simulated load option is not feasible, as some errors are triggered when requesting the actual operation on the JIRA API, and it might be too costly to do a previous verification of all possible cases.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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