Hi Reddy,
There is a bit of a work around to handle that.
First, you would need to create a separate Edit screen for that project if there is not one already. If there is one, edit it to remove the fields that you want to control the update for.
If you create a new Edit screen, just copy the existing screen and remove those fields.
Then create a new Transition screen - it's really just a regular screen that you are going to use with a Transition in the workflow.
For this new Transition screen, only put in the fields that you want to control (that is, the ones you removed in the Edit screen.
Then edit the workflow to add a new looping Transition to the appropriate status. A looping transition is a one that simply goes from the status back to the same status.
Then edit the new Transition in the workflow to add the Transition screen to that Transition. Place a condition on that transition so that only group you have identified can execute that transition and thereby edit the fields.
This is the official Atlassian approach to field-level security. Many admins have found that plugins such as ScriptRunner with its Behaviors feature gives more flexibility and ease of customer usage for this case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is no per field permissions in Jira. Follow the solution provided by @John Funk above to achieve that.
Ravi
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.