Hi,
As part of our development we want to capture the Jira-Issue revisions. for eg: we want to track the list of Revisions/History happens on the Jira Bug/Userstory. Is there a way to capture it...?
I thought of one approach I would like to create one text/numeric custom field and it should increment on every update..(jira-issue update). But I struck with this approach as increment is available with only state transitions.....
Could you please help me out.. Thanks in advance.
-Bala
There are no "revision" tracks. Issues are not static documents with clear "edit 1, edit 2, edit 3..." rules.
You need to define *exactly* what you need to think of as a revision. Yes, we can probably agree that updates to the description, summary, due date, etc are probably revisions, but comments representing a conversation? Work logs? Adding/removing a watcher? Code submits?
I don't think the concept of "revisions" is actually relevant or useful to an issue tracker. Status is important, detail is important, number of field updates... meh. But if you really do hve some valid need to think in terms of revisions, they you need to start by defining the rules of what you think is a revision before you can even start to track or code for it.
Hi,
I think that Jira already tracks all changes. You can see all changes by opening issue and choosing -> Activity -> All
Andris,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I want to capture only the Revision number, lets say if the Bug is updated twice I need some fields to give revision as '2'.
Please let me know how we can acheive this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.