"We Couldn't save your changes" when trying to save workflow edits in Jira Cloud

[Mark Paul-Sobral]

 I am unable to save any changes to the workflow I make. tried with other admins on the same project, and they had the same issue, meaning the issue's with the project, not with my account.

When I click to save on the top right of Jira, on the bottom left the pop up with "We couldn't save your changes" comes up. Can't work out why this is happening 

[Mark Paul-Sobral · Accepted solution]

Answer: Go through the workflow, look for statuses that have the same rule twice, like "Assign an issue to someone". delete the duplicate and you should be good to go. 

This other thread helped clarify it: 
https://community.atlassian.com/t5/Jira-questions/when-I-save-workflows-I-have-an-error-with-DUPLICATE-RULE-IDS-IN/qaq-p/1543170

[Trudy Claspill]

Hello @Mark Paul-Sobral 

Welcome to the community.

Are you working with a Team Managed project or a Next Gen project?

Can you describe the types of changes you are trying to make?

[Mark Paul-Sobral]

Hey Trudy, 

Thanks for reaching out. It's a team managed project, and the changes I've tried to make include:

• adding a status
• removing transitions
• deleting a status
• adding a rule

These were all done separately to try and get it to work. I can make the changes, but they can't be saved.

[Trudy Claspill]

Hi Mark,

I found this post with some troubleshooting tips.

https://community.atlassian.com/t5/Jira-Service-Management/quot-We-couldn-t-save-your-changes-quot-when-saving-workflow-in/qaq-p/1341509

[Mark Paul-Sobral]

Hey Trudy, 

Thanks for the reply, and the link. It was really helpful to start with, but didn't quite give me the answer that I needed. On further digging with developer's tools, I found the following  error code:

[{"elementType":"RULE","elementId":"151c1c20-6dcc-c70a-f7ee-f6fd606cf93d","message":"Id 151c1c20-6dcc-c70a-f7ee-f6fd606cf93d repeats 2 times in issue type 10017","errorCode":"DUPLICATE_RULE_IDS_IN_WORKFLOW"},{"elementType":"RULE","elementId":"151c1c20-6dcc-c70a-f7ee-f6fd606cf93d","message":"Id 151c1c20-6dcc-c70a-f7ee-f6fd606cf93d repeats 2 times in issue type 10018","errorCode":"DUPLICATE_RULE_IDS_IN_WORKFLOW"},{"elementType":"RULE","elementId":"151c1c20-6dcc-c70a-f7ee-f6fd606cf93d","message":"Id 151c1c20-6dcc-c70a-f7ee-f6fd606cf93d repeats 2 times in issue type 10021","errorCode":"DUPLICATE_RULE_IDS_IN_WORKFLOW"},{"elementType":"RULE","elementId":"151c1c20-6dcc-c70a-f7ee-f6fd606cf93d","message":"Id 151c1c20-6dcc-c70a-f7ee-f6fd606cf93d repeats 2 times in issue type 10015","errorCode":"DUPLICATE_RULE_IDS_IN_WORKFLOW"},{"elementType":"RULE","elementId":"151c1c20-6dcc-c70a-f7ee-f6fd606cf93d","message":"Id 151c1c20-6dcc-c70a-f7ee-f6fd606cf93d repeats 2 times in issue type 10019","errorCode":"DUPLICATE_RULE_IDS_IN_WORKFLOW"},{"elementType":"RULE","elementId":"151c1c20-6dcc-c70a-f7ee-f6fd606cf93d","message":"Id 151c1c20-6dcc-c70a-f7ee-f6fd606cf93d repeats 2 times in issue type 10020","errorCode":"DUPLICATE_RULE_IDS_IN_WORKFLOW"},{"elementType":"RULE","elementId":"151c1c20-6dcc-c70a-f7ee-f6fd606cf93d","message":"Id 151c1c20-6dcc-c70a-f7ee-f6fd606cf93d repeats 2 times in issue type 10023","errorCode":"DUPLICATE_RULE_IDS_IN_WORKFLOW"},{"elementType":"RULE","elementId":"151c1c20-6dcc-c70a-f7ee-f6fd606cf93d","message":"Id 151c1c20-6dcc-c70a-f7ee-f6fd606cf93d repeats 2 times in issue type 10022","errorCode":"DUPLICATE_RULE_IDS_IN_WORKFLOW"},{"elementType":"RULE","elementId":"151c1c20-6dcc-c70a-f7ee-f6fd606cf93d","message":"Id 151c1c20-6dcc-c70a-f7ee-f6fd606cf93d repeats 2 times in issue type 10016","errorCode":"DUPLICATE_RULE_IDS_IN_WORKFLOW"}]

Essentially, what it boils down to is that there were 2 rules in one status that was causing the issue. Atlassian could do with elaborating their error message with more than just "We couldn't save your changes", and that would have saved a lot of time. 

[Mark Paul-Sobral]

Thanks for the help with it all, Trudy :)