Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Custom field edit restriction based on user/role permission

Is there a way I can restrict custom field edit based on user/role permission  in jira cloud?

suggestion please!

3 answers

Not out of the box.

However this is the method that can be used to restrict who can edit fields, if you don't mind creating a button for editing the field. It requires you to create transitions for every workflow associated with the issuetypes you want the field restricted on. See instructions with pictures below.

 


Step 1: Create the Screen with the Restricted Fields

  1. Select Add Screen.
  2. Give it a name/description and add all the restricted fields in it. 

1_screencreate.png

Step 2: Create the Transition with the Restricted Field Screen

  1. Edit the workflow of the issuetype.
  2. Select + Add transition.
  3. In the "From status" section, select Any status.
  4. In the "To status" section, select Itself.
  5. Give the transition a name. This name will be used on the button that will activate the screen on the issue (and allow someone to edit the field).
  6. In the "Screen" section, select the screen created in Step 1. Save your changes.
  7. The transition should look like an infinity loop of sorts.
  8. Click on the transition and select Conditions. You will be redirected to the transition edit page.
  9. Select Add condition and add the permission rule you want to execute for this button. Note that this rule will indicate who can see the button and therefore, edit the field.
  10. Publish the workflow.

2_workflowtransition.png

Step 3: Remove the Fields from Your Edit Screen

Lastly, navigate to your edit screen and remove the fields you want to restrict. You will need to create separate "view"/"edit" screens for your screen scheme if you haven't already because you may want the restricted field to remain visible when viewing the issue.

 

Once all of this is completed, you should see the button like so.

3_result.png

Clicking on it will bring up a transition screen with the "restricted field" on it to which you can make changes and add a comment.

4_result.png

Kishan Sharma
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 14, 2022

Just wanted to appreciate the detailed answer @Vera with screenshots, thank you!

Like Vera likes this

Vera, this is awesome. I swear I followed this to the T but I am not having a button pop up but I am going to review each step closely and see if am missing anything!!!

0 votes
Ben Wade
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Nov 23, 2023

@Vera HI Vera,

could you please help with this part: "You will need to create separate "view"/"edit" screens for your screen scheme"
can you show step yb step how to do it?

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 18, 2022

No, Jira does not have field-level permissions.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events