Can you create a Jira "Tag" like SVN tags?

[Christopher]

We are looking to use Jira+RTM for issue tracking and requirement & test management. Is there a way to create a snapshot (tag in the SVN sense) of the jira database? I know the entire database can be saved off at a particular point in time but this requires significant memory where tags, at least in SVN, are relatively cheap. I've looked at sourcetree integration with Jira but this doesn't seem to be what I want. 

[Bernhard Doleschel _Ease Solutions_ · Accepted solution]

Disclaimer: I´m from Ease Solutions, the vendor of R4J - Requirements Management for Jira.

Hello Christopher,

Jira offers you good options for simple Requirements & Test Management, but there a important features missing like structuring, coverage analyses and (as you call it) snapshots. We call them baseline in R4J - Requirements Management for Jira. So you can assign a free text baseline name to a whole project or parts of it (selected by the structuring option via folders and filters).

If you interested in a free demo about this and many more features please let us know via our service desk.

Best Regards, Bernhard

[Christopher]

Thank you for the insight. How does the baseline work exactly? Does it create a new Jira issue and then have a compare function? Do you see the past baselined issues inside the project or only the most recent ones?

[Bernhard Doleschel _Ease Solutions_]

Hello Christopher,

baselines are stored in our R4J tables (inside Jira database) and only access-able from within R4J (which is just a click away from you Jira views). There you have comparison options and you see for each baseline all issues with the state/value when they´ve be captured. If a issue is removed from current project, you still have the data in the baseline. If you like you can have a free demo, please contact me via our service desk.

Have a great day and weekend, Bernhard

[Nic Brough -Adaptavist-]

No, Jira is an issue tracker, not a source-control system.  It tracks all the changes to issues, but the focus is on issues, not change, so there's no tagging of a "version" of an issue.