You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have added a behaviour script on Assignee field to make it read only when a custom user picker field has a value.
The script is working fine on Create and Edit Screen, but it does not work on Assign Screen.
I have tried saving the script as server side as well as Initializer, but got same results.
Also, is it possible to restrict 'Assign to me' functionality using behaviour scripts?
Any help would be appreciated
Regards,
Swapnil Srivastav
Hello,
behaviours work only on create/edit/transition screens, so no luck for assigning I guess.
The workaround I guess would be restricting assigning overall and creating your own "assign" transition.
Not really a solution for your problem, but might set you on a right track as well:
you can restrict option to assign issue overall on a certain status using workflow properties
by adding this property to a status: jira.permission.assign.denied
Hello @Ilya Turov ,
Thanks for your response.
I got it done on the Assign screen as well. Behaviours work on Assign Screen as well
Best Regards,
Swapnil Srivastav.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Guess I was wrong, good to hear.
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.