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
Hello all, I have read a couple of post and wasn´t able to find a way to achieve what I want.
I want that if the status of a ticket is in "working", there is no way to edit one of the custom fields .
Out of the box, you can't achieve that, since Jira do not provide field level security and editability per se. There are solutions and workaround which I describe below:
Let me know if any of the above solution would be suitable for you.
Let's examine the 3rd case which is doable without any additional app:
First of all you have to get rid of that specific field from the edit screen. With that said the user will be able to enter in upon issue creation and only view it within the new issue view (clicking it, will not go into edit mode).
STEP 1: To do that I would go to project settings > screens and click the individual screens to edit them and to make sure that this field will be only visible on the create and view issue operation:
In that point you would want to try open an issue of that specific issue type and try to see if that field is editable (it shouldn't be).
STEP 2: Go to cog > issues > screens > add screen. Give it a name and edit it so as to add your field to that screen:
STEP 3: Next step is to edit our workflow. Head on to project settings > workflows, and click that pencil icon of the specific issue type:
The results are shown below:
Initial status with the Edit Client transition visible.
Clicking it will popup the screen to edit it
On the In Progress status the field is locked, since the Edit Client transition is not visible:
BUt on the next status (or any other status) the transition will be available
Hope it helps. Took about 25 minutes for this reply :D lol
I tested out this scenario which works pretty well.
1. I created transition screens to map to my individual "in progress" states
2. I used the security property "jira.issue.editable=false" for each of those states
What I have now is allowing users to edit specific fields configured in the transition screens only. Once the transition is completed and the screen defined as my VIEW screen is displayed. All the filed accept for Assignee is secured. I don't know why Assignee can't be secured, but of well.
I use to work with a application called Synergy Change and I remembered that's how it was setup to bring security over fields within the states. And I think there was a number of required field settings in that configuration. Man, these workflow tools are a beast to manage.
@Alex Koxaras _Relational_ does this only work for custom fields? I.e I followed all of the steps you had here to limit the editing of the story points field once an issue moves to in progress and it would not work for me. I can continue to edit that field regardless of the status it is in.