Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,435
Community Members
 
Community Events
184
Community Groups

Can someone help me create a script so that Assignee cannot be the same user as the User Picker?

I'm using a User Picker one of my projects and at any point of the workflow, I do not want the Assignee to be the same user as the user in the User Picker field I have.  I have no idea how to start a script like this and I'm hoping someone would be so kind to share or show me how to develop a script for this.

1 answer

0 votes
Jeroen Poismans
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 08, 2021

Hi,

Can you provide some extra info:

  • Is the User Picker field on the Edit screen, in other words can it be changed with an issue update or only in a transition?
  • Same question for the assignee.

I am asking because if you want to do this kind of validation, you would have to have a "trigger" event for the validation BEFORE the issue is updated.

The update of one of these fields can not be the trigger because by then the value would already have been changed, in other words the validation would be too late.

You can do the validation when these fields are updated in transitions. 

 

Regards,

Jeroen

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events