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
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?
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events