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?
Hello @Solaris_9
Welcome to the Atlassian community.
Why are you setting newly released Versions to Archived? Why not set them to Released?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.