Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Dear community
We just installed Jira SW and are really happy we did it! Some content was already created and therefore I have some question which I am sure you can help me with.
We want to do a copy of the "fix version" field and call it "found in version" to separate in which SW versions we found the defects and in which SW versions we solved them.
For the copy of the field "found in version" which we want to add, we would like to link it with the same list or releases which is already linked to "fix version".
Does anybody know, how we can create a new field similar to "Fix version" and link it to the same release list? This would really help us and ensure that we have a gapless defect management.
I really appreciate if you can help me with that.
Best regards
Nik
Hi Niklas,
You should / can use the Affected Version system field as a counterpart of "Fix Version".
Further information on General use of Affect Version/s and Fix Version/s KB Article
In addition, system administrators can create custom fields of type version that will mimic the behaviour of the Affected Version field as shown in the picture below:
See Create a custom field page to learn how to do it.
Regards
Dear Jack
Thank you for your answer. It helped me a lot. I just created a new Screen scheme for the issue type I need "affects version" for. Really good and it is also directly linked to the same release list, that "fixed version" is linked with. Thanks a lot for your support. :-)
Regards
Nik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're welcome Nik :)
have a nice day!
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.
@Jack Nolddor _Sweet Bananas_, what do you use for "found at"? i.e., bug was found at what part of testing? (other than in the comments) Would be helpful for lessons learned data.
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.