Hi,
What is the best practice to use the "Affected Version" field for managing SCRUM development including: epics,stories, sub-tasks, bugs and features?
What issue types use this field?
How do you use it?
Thanks,
Janiv.
Fix Version(s) is be design used in JIRA for denoting two things:
- when issue is "done" -> in which version of the software something was implemented (a bug fixed, a feature added)
- when issue is not "done" -> in which version we currently plan to include given fix/change/story
Dualism :) Works suprisingly good in practice.
Affected Version(s) is mostly used just for marking which version given bug or problem has been spotted in or sometimes which version given (planned) change referrs to.
Most of JIRA built-in reports, gadgets and views assume that Fix Version(s) field is used for tracking your plans and past achievements - like Change Log or Roadmap, Burndown charts in Greenhopper, Version Workload report, etc.
Using Affected Version(s) for this thing is like swimming upstream. I don't recomment it.
Typically Bugs. The field is used to denote versions that are affected by this Bug!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks,
What about stories and tasks, how do you tell which task/story belongs to which version (hence, implementation is targeted to a specific version)?
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That would be Fix Version(s) field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A small discussion around it: http://forums.atlassian.com/thread.jspa?threadID=45023
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, being an issue tracking system, JIRA mostly talks the language of Bugs. Whether an issue (or story) is actually fixed or Done or rejected is determined based on its resolution. Fix Version(s) just points to its the version in which it was done/fixed.
You also have the option to change the language system wide by translating JIRA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, It seems wierd to use "Fix Version" for something that is not fixed but done (i.e.: story, epic, task).
The discussion you directed me talks about bugs, I'm talking about other issue types.
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@janiv,
From a usage pov we actually first set the Affected Version whenever a new item comes to the backlog. This is mostly the version in which the customer expects it to be present. But finally, in which actual version it get out of the product is decided by the FixVersion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.