Hi there,
my company evaluates on how to use Jira as a requirements management database tool. We understand that there is a simple recommendation on how to do it
https://confluence.atlassian.com/jirakb/using-jira-for-requirements-management-193300521.html
The features we miss the most is the possibility to have named versions for requirements. I understand that you can change an issue and there is some kind of history recorded for an issue. However, we need means to tag a specific version number or baseline-tag to a version of a ticket. All changes to all possible fields of the issue need to be versioned to that version identifier. Additionally we need the tools to compare specific versions of the issue to each other and get a proper diff view. Or we need the possibility to go back to any named version of the issue in all the fields at that point in time. Implementing such thing seems pretty difficult with jira.
Is there any best practice on how to deal with the versioning issue in the context of requirements engineering within Jira? Is there maybe any (proprietory) extension/app/plugin that adds these feature to create a proper requirements engineering experience?
Cheers,
Hauke
