nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Configure field security permission

S_3e95q9

Hi,

Is if possible to configure or restrict users that don't belong to certain role from editing certain fields on Issues?

For e.g. User in Quality role can only edit "Defect Comment field"

Users in Logistics shouldn't be allowed to edit "defect comment feild"

Any reference link will be very helpful... I'm using JSD Cloud.

Thanks for help

Accepted answers

Nic Brough -Adaptavist-

Jira does not have field level security.

The best you can do is move it into the workflow (so people have to use the workflow to get to edit fields, and the workflow can have "conditions" that can protect the edits)

All comments

Nic Brough -Adaptavist-

Jira does not have field level security.

The best you can do is move it into the workflow (so people have to use the workflow to get to edit fields, and the workflow can have "conditions" that can protect the edits)

S_3e95q9

Thanks @Nic Brough -Adaptavist-

I'm looking for a reference article / implementation example, if you are aware of any please share... thanks

I've used conditions in WF for roles but not sure how can field be implemented.

Nic Brough -Adaptavist-

Ok, so if I were to do this from scratch, I would

Choose my field that I want to protect. Let's call it "Pet-type"
Create four new screens (making liberal use of copy), with names and content such as:
- Screen-c: Has all the fields I want the users to give me when creating an issue (maybe including pet-type)
- Screen-e: Does not have pet-type on it
- Screen-l: Definitely has pet-type on it
- Screen-T: Has only pet-type on it
Then you set up a screen scheme that says
- Create: Screen-c
- Edit: Screen-e
- View: Screen-l
And use that in the issue type screen scheme for whatever issue types you want to protect pet-type for
Now edit the workflow, and for every status that you want to allow edit of pet-type in, add a transition that goes back to the same status with:
- Name: edit pet-type
- Screen: Screen-T
- Condition(s): Only group or role X can use this transition

You'll now find that people who match the condition can "edit" the pet-type. Downside is it litters the history with "status changed" when it didn't, and you have to tell your people to look in the workflow for editing it.

S_3e95q9

Thanks @Nic Brough -Adaptavist- its a good curve ball!

Peter Atthem

Hi,

You can now use Protected Fields: https://marketplace.atlassian.com/apps/1226228/protected-fields?hosting=cloud&tab=overview to managed View / Edit permission for fields.

Note it works in the new Issue View / Editor.

Best regards

Peter

Brooke_7n1mi8

Hi Peter, does this work with team-managed (next-gen) projects?

Thank you

Brooke

Takafumi Ohtake -Ricksoft-

Currently, there are apps that enable "field level security" for Jira Cloud.

Field Level Security Apps for Jira Cloud

With the apps, You can hide fields and make fields read-only based on user, group, project role, and so on.

However, if you just want to make fields read-only and you don't mind complicated configurations and UI, the workflow solution that Nic explains is the best solution.

If you want to hide fields, I think the current solution for Jira Cloud is to use one of the apps.

(Please note that I'm one of the folks behind Ricksoft that is the vendor of one of the apps.)

Lisa Adams Savard

i actually purchased your app and im impressed with the UI for adjusting access to custom fields. Unfortunately i also use Power BI integration for advanced reporting and now those fields wont export. Is there a work around or a possible feature on permission to allow it to export with a data connector like Power BI Connector for Jira by Tempo Software Platinum Marketplace Partner

Georges Petrequin

We built a free app that helps address the field-level security problem in Jira Cloud: Protected Custom Fields

It lets you control which users can view or edit specific custom fields, and also includes an audit log so you can see who accessed your protected fields and when.

If you need to restrict visibility and editing of custom fields to specific people but want to avoid locking down entire work items, it's worth a look!

It's completely free, runs on Forge, and if you have any questions or feedback (or want a quick demo), just email me at gpetrequin[@]adaptavist.com

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-desk

jira-service-desk-cloud