Affects and Target version

[Dan Hartnack]

Is there a generic field like the Affects Version field that can be applied to a project in the same way? I am want to set up another field in a project that is Targeted Version but still uses the same information from the Affects Version field without having to make a custom field and populate with every version of our software.

[Nic Brough -Adaptavist- · Accepted solution]

Depends on how you use "fix version" - some people use it for "this was fixed in" and others "we aim to fix this in". Both approaches have advantages and disadvantages.

Some teams would benefit from a third "target version" as well. If you do, then I recommend that you use "fix version" to say "this was fixed in" and "target version" for, well, um, where you'd like to fix it. This because fix-version feeds into other things like release notes, planning, agile and so-on.

To do this, you can simply add a "version picker" custom field. It will use the same list of versions as affects versions and fix versions automatically...

[Greg Solovyev]

@Nic, doing what you are suggesting breaks the scrum board and version burndown reports. How do you keep those working AND have Target Version field at the same time?

[Jobin Kuruvilla [Adaptavist]]

You can create a custom field of type Version Picker.