In some cases, when a configuration is imported some issue data related to workflows may become inconsistent. This problem affects Project Configurator versions until 1.12.1-JX. If you are running one of these versions, please upgrade as soon as possible to a newer one (scheduled for May 4th 2016). Keep reading the rest of this article for further details.
This problem will occur when all these conditions are true:
If all these conditions hold, the configuration import does not update correctly the existing issues to the new workflows.
The easiest and most immediate way is using a version of Project Configurator where this issue has been fixed. If this is not possible, follow this advice:
The visible effects vary depending on the exact difference between the new and the old workflows assigned to the issues. They may include some of these:
When viewing the issue the JIRA log shows a message like this:
Run this query on the JIRA database, where 'XXX', 'YYY' are the keys of the projects you want to check:
This query will return all existing combinations for any issue of:
Compare, for each project, this result with its current workflow scheme (see below image). If the associations reported by the query differ from the mappings defined in the workflow scheme, then your instance is affected by this problem.
This problem can be fixed quite easily. For each affected project, repeat these steps:
If several projects have to be fixed, and some of them share the same workflow scheme, it has to be copied only once (step 1 above).