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
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
In one of our projects, there is a requirement to not edit filed by the user of the JSM cloud.
Assignee value should get from the custom field and based on the status of the workflow.
For this I just removed Assignee field from the Edit Screen of the corresponding issue type. But still the Assignee field is editable in the ticket. I'm missing something here.
Did anyone tried this before? I need to do it without any Add-on in our cloud instance.
I would change the permissions for your project so that no one has permission to edit the assignee field except for the user Automation for Jira. You'll need to update the "assign issues" permission. Then use an automation rule to set the assignee when it enters the desired status.
There is a permission setting:
Ability to assign issues to other people.
It allows you to manage who can assgn an issue. If you want to restrict who can do this, it is the way to go.
If you want to apply this to only one (or selective) issue types, then you can use the workflow properties on the statuses on which you want to make the assignee field uneditable. You can use the following property.
jira.permission.assign.projectrole -> value=<project-role-ID> (To only allow the users in the particular role to change assignee)
jira.permission.assign.denied (To disable for everyone)
Bonjour, la solution que vous donnez fera qu'aucun des champs du ticket ne sera modifiable , non ? Comment vous faites pour faire en sorte que juste un certain champs n'est pas modifiable ?
Hello, the solution you give will do that no fields will be editable, right ? How do you do so that only one specific field shouldn't be editable ?