I am new to Jira, but have addressed this previously in TFS. I work in a heavily regulated environment, where there is an expectation to have a definitive set of specifications for every release that was delivered to production.
Because of the nature of an agile system, the focus is more on what changes in the next iteration as opposed to keeping a running document of all the stuff already there plus any changes.
The typical way I have seen this done is to let the dev team work in the agile tool and separately assign a BA to mirror what is happening in the agile release by updating a word document. Of course this is not productive. Better for there to be a way the agile system can always produce the full set of "specifications" for any release.
The way that seems most obvious to solve this is to have every issue representing specifications to have a released in release and a removed in release pair of fields. Thus the report of the specification set for any release X is simply the list of all issues where released in release <= X and removed in release is empty or >= X.
Note that in order to change a specification, we would clone the original, make changes as needed, then set the old issue to removed in release = this release and the new issue released in release = this release.
However, it does not seem there is an easy way to do this. As far as I can tell, there is no ability to add a custom field of type release (i.e. connected to the Jira releases). The workaround would be to use a Select List and just keep the values in it synced up with the releases. Is that the recommended option?
Is there a better way to do this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.