How to freeze a version of jira contents so that it can be fetched later

- we would need to be able to identify the version of each element in jira base - we would need to be able to fetch the version of elements later on even if Jira content has been updated later As an alternative, is there a way to "intelligently " dump the wanted version of of whole jira contents and compare later which element have changed ?

1 answer

0 votes

Dropping a whole database out just for this probably can't be called "intelligent", and the closest you can get using OnDemand is to export it daily (and then you're into painful scripts which will be hard to maintain on upgrades, or recreating entire system copies to do the compare in any useful way)

Assuming by "elements" you need fields, then you can do things like "field WAS X" to find them. Jira keeps a full history and there are number of ways of getting at it. But you'll need to thnk carefully about what you want and why.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,799 views 11 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot