Fastest way to compare automation rules differences between test and prod.

Ari Raatikainen
Contributor
July 15, 2024

Hi,

I have a customer having two Jira instances, one for test and another used in production.

They are having over >100 automation rules. These automation rules have changed over time, resulting in some major differences compared to production.

What would be the recommended way to determine the differences? I know you can export all rules, but comparing JSON files is quite challenging. Would you recommend reviewing all the rules one by one in Jira?

1 answer

1 accepted

4 votes
Answer accepted
Bibek Behera
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 15, 2024

@Ari Raatikainen ,

I would suggest checking the automations one by one manually and tag them using lables once confirmed. Otherwise, it will be difficult to compare the json files as the ID are most likely different in sandbox and production.

If you don't want to end up messing up existing data due to the wrong implementation, and then manually check for what went wrong take the first step of using a manual approach. Just go for the single project-specific rules first, then cross-project then global.

 

-Bibek

Ari Raatikainen
Contributor
July 15, 2024

Thanks Bibek. I'll do what you suggest.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events