The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Fix version

Manikandan
January 1, 2024

I made fix version as mandatory field. But when i get bug which is not a bug or duplicate still i am asked to update the fix version. So what fix version to be used for not a bug or duplicate bug

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

2 votes
Answer accepted
Kavitha Chandrasekaran
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 2, 2024

Hi @Manikandan 

Another way to do this, is not make the Fix Version as mandatory field, but keep it as optional. Add a rule when moving status to Closed (or similar), if the resolution is not duplicate/not required etc then the field value will be required. 

Manikandan
January 3, 2024

@Kavitha Chandrasekaran - Thank you 

1 vote
Antuan Sammak
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 2, 2024

Hi @Manikandan 

 

you can create a fix version with a relevant name and mark it as released, then add all similar tickets (not bug, duplicate) to this one only.

 

that will also help you to run some reports on this fix version at some point to know how many invalid tickets you have received.

 

Regards,

Manikandan
January 3, 2024

@Antuan sammak - Thank you