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: 

Is it possible to reject duplicate values among different custom fields?

Jim Fung
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!
July 22, 2024

Our issues are configured with multiple custom fields, each of which is a multi-version picker. The constraint that needs to be enforced is that there cannot be duplicate versions among the different fields.

For example, if a user attempts to enter version “V” into multiple fields, that should not be allowed and immediately fail.

Another similar case is if a user attempts to enter version “W” into a field, but it already exists in another field, for that also to fail.

Bonus points if this can be done in a customizable way, e.g., apply the constraint to specifically named fields only.

Thanks in advance

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Mohamed Benziane
Community Champion
July 24, 2024

Hi,

Welcome to the community

I think you can make it work with Behaviour Behaviours (adaptavist.com)