Can a change to transitions of statuses in one workflow impact other workflows that use same statuses

[Sam Hall]

Hi Lakshmi,

Can you give some more information of what the 'validations' were? I think you'll need to be more specific to help the community answer.

Were they "Field x is required" type messages?

This can happen if projects share the same field configuration, and you make a field "required" but it is not part of the screens for a particular project. it's the sort of problem solved in this question/answer: https://answers.atlassian.com/questions/198777.

Your other option is to contact Atlassian directly here.

Sam 

[Lakshmi Pratha Hari]

Thanks Sam, 

We had configured separate workflows for different projects in our Jira (Cloud). We had also configured separate schema thereby ensuring one project doesn't impact other.

Over the last week we had added custom fields and Workflow transitions in one project. We noticed that this impacted the other projects. Note that both projects have separate schema and no change was done in Default schema or default workflow.

Yet, there was an impact. Other workflows were getting the same validations for fields that is not configured to their screens or workflow transitions. 

We want to understand what caused this so that we can be careful in applying future changes. We checked audit log and it didn't provide any information for this problem. Please let us know how we can understand the problem.

Regards,

Lakshmi Hari 

[Sam Hall]

Workflows are independent of each other, so editing a transition in one workflow won't impact other workflows.

You should note that a workflow might be used by more than one issues type / project, though, so check the workflow schemes to see where it is being used.

If you change a status name it will affect all workflows it is used in.