It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can I version control a User Story (Issue) in Jira?

I want to be able to apply version control to an issue in JIRA - is that possible?  The business will sign off a version of a user story but this may need to be changed at a future date but we need to retain the original version (signed off by the business).

5 answers

What elements on the issue are you talking about version controlling? The summary and description?

Yes, if possible.

I don't think that's possible and it seems strange you'd want to to be honest. It sounds like you're using the summary and description to keep detailed requirement and specification information given that you want to version control it, which I personally don't think is how it's intended to be used. I would advise using the fields to only give a brief overview of what you're trying to achieve in the user story, not a detailed spec. You can then either link off to a confluence page with the detailed requirements / specifications, which are naturally version controlled (assuming you have confluence), or link / attach detailed documents which you could version control in another document version control solution, or even something like SVN.

JIRA does keep the full history, so you do have older versions available, but there is no versioning control as such, only the date of the change and who modified the fields.

There is an AddOn RMsis that may help you, but it is paid for and may be overkill.

WHERE and HOW do we get access to "JIRA does keep the full history"???

This is a simple ask, ala RALLY.  Where who did what to features and user stories from inception to closure.

You can capture the signed-off version with the PDF Automation Plugin!

Create the following automation rule:

  • trigger: when the issue takes the transition "sign off" (or however you implemented the "sign off" concept),
  • action: run the "Attach PDF Action", create a PDF from the issue's most current state, and attach that to the issue. You could even generate a timestamped name like "STORY-123-20160225-1305.pdf".

From this moment, the issue can be changed any time, the signed off version is there in the PDF document!

See this section to set up the automation rule:


Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

274 views 1 2
Join discussion

Community Events

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

Events near you