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.
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG