Out of the box the only way is to put the field ONLY on the transition screen where X will see it. I presume you are somehow restricting the transition to user X or just want the user executing the transition to edit the field. Out of the box, JIRA doesn't have field level permissions. The behaviours plugin may allow it.
Thanks for the response Joe.
Scenario:In the transition executed by X, there are field values which Y should not be able to edit though Y is the assignee. Also, X should be able to edit the fields even after the transition.
I don't see it happening without a plugnin. Removing field from the edit screen is not an option.
What you're describing there is summarised as "field level security"
JIRA doesn't do that.
There is a field level security add-on by Quisapps which is well worth a look.
I'm able to use behaviors module in ScriptRunner to make a field not editable.
Here's what I did:
Created a behavior, mapped to a particular project, made it read-only and added the condition except current user is username.
By doing that, except the selected user no one can edit the field from edit screen but all are able to edit from inline editing option.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events