You will have to limit the Users/Groups/Roles that you put in Schedule Issues and Edit Issues Project Permissions. These permissions will give users the ability to do so.
Complete documentation can be found here https://confluence.atlassian.com/agile/jira-agile-resources/jira-agile-faq/what-are-the-permissions-used-in-agile-boards.
You will just have to update your "Edit Screen" to restrict what fields can be edited anytime. You can also restrict fields being edited based on your an issues status by apply Workflow Properties (https://confluence.atlassian.com/jira/workflow-properties-189949.html).
Gabrielle, thanks for your help! What is the property key we need for the transition to disable access to that field? Right now I'm working with a property key of jira.permission.edit.gh-sprint.group.1=Developers and a property value of false on a transition in a particular Workflow, but it doesn't seem to be functioning the way I expect it to, even though I'm testing with a user in the Developers user group. Is my property key and value correct? If you can help me correct or confirm that, I can do the rest of the troubleshooting. Thanks!
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs