Useless status mapping requested when workflow is changed

[Pierangelo Repetti]

Hello,

sometimes it is needed to change the workflow scheme for a project and sometimes the statuses do not completely match, so the wizard is asking to re-map the dubious ones, showing the message

The current status of each issue needs to be changed so that it is compatible with the new workflows.

The wizard is also showing the number of affeted issues for each type.

It often happens that there are no affected issues, all numbers are 0.

Why is the wizard asking for a remap then ? Couldn't it just go on and change the wf silently ?

And: what happens if you just accept the proposed default mapping when you see that no issue is affected ?

Thanks

[Walter Buggenhout · Accepted solution]

Hi @Pierangelo Repetti,

Yes, you are right. The wizard does indeed offer mapping options that are not always necessary. If you leave the default settings in place when no issues are impacted, nothing wrong will happen.

Be aware though that you are pushing configuration changes in a live system. While you may be going through the steps to push the new workflow into production, users may be at work in the live environment that you are about to change. when the wizards ask you to define every possible scenario, it takes this into account, which is - if you were to ask me - a conservative approach, but a good one. If the wizard would not ask you to provide this full mapping and ongoing work in your system leads to inconsistencies because you aren't asked to provide mappings for ongoing changes and you end up with erroneous data, you would probably not be happy with data ending up wrong.

So, consider it the safest approach. As an administrator executing the change, you can still choose not to perform mappings you consider not useful.

Hope this helps! 

[Pierangelo Repetti]

That makes sense, thank you.