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

Antti kokkinen

- 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 ?

Nic Brough -Adaptavist-

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.