Control some fields in certain phases

[Mohamed Saad Taha]

Dears,

I ask this question many time without any result 

How I can control which fields or section in created issues can be edited 

for example, if I want to close only some fields in the requests not to be edited by any one once issue create and allow some others 

what i can do is to disable editing all fields in the requests

[Mohamed Saad Taha]

Dear Javin,

for example, if I want to only allow editing in people section and close any other modification 

[Jovin]

Hi @Mohamed Saad Taha 

You can achieve this in certain circumstances, but not individually in the manner you may be thinking. Below are some solutions:

• Automation Rule with trigger "Issue Edited" to "undo" edits to a field
  • Have an automation rule that monitors fields you don't want edited and then check whether it was modified, you can then use the changlog smart value to revert the field value back.
  • https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog-- 
• Update the screen scheme to split the View/Edit Screen
  • By default Jira has a combined View/Edit Screen which dictates what fields are visible and editable on the view/edit screen. You can split this into 2 - a view screen and edit screen. Any fields you include on the view screen, but exclude from the edit screen will become view only.
  • https://support.atlassian.com/jira-cloud-administration/docs/manage-screen-schemes/ 
• Using Status Properties
  • You can make the entire issue read only or editable only by certain people by leveraging the edit property for the statuses you want to control things in. This is good for when you make an issue closed, or under review and you want to prevent edits.
  • https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/ 

Hopefully this helps!

[Mohamed Saad Taha]

HI @Jovin ,

thanks a lot for your comments but unfortunate all is not what I need 

[Jovin]

@Mohamed Saad Taha - can you perhaps expand on your needs with a more thorough example?

Such as:

I want to be able to prevent a tester from updating the status of a story until the developer has transitioned it into "Ready for Test".

I want to make it so only Tech Leads can update the story points of a story after it has left the "Ready to Start" status.