Hi Community,
I have a custom Reviewer field that is multi-picker user select. This role must be unique/independent of the Assignee, currently this separation is being handled manually through Managers etc.
Is there anyway to have the field be unable to be the same as the assignee ? Like a must not equal comparison?
Running Jira cloud premium and looking to solve without additional plugins.
TIA
Hi Tom - Welcome to the Atlassian Community!
I assume the Review field is getting populated manually and not through automation?
Regardless, there is not an out of the box way to prevent that. The best you can do is create an automation rule based on a Field Value Changed trigger (the field being the Reviewer field and the Assignee field). Then add a condition to check that the Assignee is in the Reviewer field. Then send an email to the initiator (the person who changed the value) and probably you that lets them know this is against the functional rules.
Then you or someone can update the Reviewer field to remove the Assignee.
Yeah the automation route was one I was thinking to take but was hoping for a transition logic block / validator.
Thank you for your answer, I hadn't considered an on change trigger just a schedule, I will do both.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Tom Smith
Not natively as far as I know.
You could use Automation as a workaround? For example...
You could potentially combine (2) and (3) together also!
---
Would something like this work for you?
Ste
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.