nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Best practice for using Affected Versions

GilK

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.

Accepted answers

Wojciech Seliga

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.

All comments

Jobin Kuruvilla [Adaptavist]

Typically Bugs. The field is used to denote versions that are affected by this Bug!

GilK

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,

Jobin Kuruvilla [Adaptavist]

That would be Fix Version(s) field.

Jobin Kuruvilla [Adaptavist]

A small discussion around it: http://forums.atlassian.com/thread.jspa?threadID=45023

Wojciech Seliga

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.

Using Affected Version(s) for this thing is like swimming upstream. I don't recomment it.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

version

best-practice