How to create a specific restriction for a Jira field

[Chethana Hashani]

Hi all,

I have created fix version as a mandatory field for any type of jira ticket and it is related to "In-progress" to "Done" transition (when a developer moves a ticket from "in-progress" status to "done" status, it is mandatory to set fix version). Now I need to create special restriction for re-opened tickets. If a ticket is re-opened and after re-fixing it, when a developer tries to move that ticket in to the "done" status again, they are not allowed to keep already released fix version in the "fix version" field and should pop up a message asking for an upcoming release version. Can I do this?

Cheers,

Hansi

[Gregor Kasmann_Actonic]

This is an expected behavior of Jira, where it is possible to add issues after a version is released.

However, there is a open request for the feature to fix this. You can access it here: https://jira.atlassian.com/browse/JRACLOUD-5830 

[Chethana Hashani]

Hi Gregor,

Thanks a lot for the info :)

Cheers,

Hansi

[Alexey Matveev]

Hello,

I think if you want to do it out of the box, you can clear the fix version field on reopening an issue. And then your mandatory rule will work again.

[Chethana Hashani]

Hi Alexey,

That's a great suggestion. Can I do it automatically? I mean, when re-opening a ticket, can I make it mandatory to ask QAs to make the fix version field empty? Also is there any specific place in the ticket which I can use to track the previous releases which the ticket had been assigned to?

Cheers,

Hansi