Affects Version: mandatory checking and archived versions

Solaris_9
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 21, 2024

We implemented the mandatory checking on the field "Affects Versions" to make sure a version must be provided when the issue is created, and it's not allowed to change to make it well tracked.

If we have one version named as "VERSION001", and we have an issue "TICKET-001" which was created in this version. But before releasing to customer, this issue was not able to be solved. Thus, it was postponed to next release, so now the Affects Version = VERSION001, and Fix Version = VERSION002. 

Then VERSION001 was released to customer with a restriction TICKET-001. and the version was archived.

In next version VERSION002, when we want to re-visit the issue TICKET-001, things become weird. Since Affects Version is mandatory, and VERSION001 was archived, the TICKET-001 can never be able to edit anymore, because the archived version will not be regarded as the value of Affects Version.

so, my question is, how to include the archived versions when performing the mandatory checking?

 

Snipaste_2024-11-22_13-25-27.jpg

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 22, 2024

Hello @Solaris_9 

Welcome to the Atlassian community.

Why are you setting newly released Versions to Archived? Why not set them to Released?

Solaris_9
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 22, 2024

Hello @Trudy Claspill

because we don't want any new ticket can be created on this version anymore. If we set the version to Released, it can still be selected in the Affected/Fix Version, this is what we don't want.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 4, 2024

Hello @Solaris_9 

Can you clarify the following statement?

Since Affects Version is mandatory, and VERSION001 was archived, the TICKET-001 can never be able to edit anymore, because the archived version will not be regarded as the value of Affects Version.

Are you saying that when you attempt to edit TICKET-001 the Affects Version field is cleared? Or that it can't be edited? Or both?

The design of Jira is such that you cannot newly add an Archived version to a Version field. I did find this change request which Atlassian has marked as Closed/Won't Do.

https://jira.atlassian.com/browse/JRASERVER-36591

Suggest an answer

Log in or Sign up to answer