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; } } }

Add custom field to Modify issue screen

KP11

We have a group(Developers) that cannot view custom fields under the Modify Issue button on a workflow. We are trying to add the view so they can update the fields. How do we trace where to add the view. What roles or permissions need to be changed and where? I only see modify reporter under permissions.

I added the custome field to the configure screen area. Is this correct or are there any other permissions? Prior to this only certain groups could view the fields. What other thing control the view since now its viewable to everyone. Is thys a secuirty screen by group, roles or some other level?

http://jira.atlassian.com/secure/admin/ConfigureFieldScreen.jspa?id=10200

Accepted answers

All comments

Nic Brough -Adaptavist-

I'm going to assume that "modify issue button on a workflow" means that you have a customised workflow to which you have added a transition called "modify issue"

If that is incorrect, then you need to correct me, and explain what you really meant to describe (bear in mind that we do NOT know your system, most importantly, how you have configured it differently from a Jira install off-the-shelf)

There's actually quite a lot wrong with your question. You are assuming that "developers cannot view custom field". Quite simply put, Jira does not do that.

It will do some limited "prevent edit" stuff on reporter, assignee, versions and due dates, but NOT custom fields. This invalidates most of your question, because there is no "view by everyone", "security scheme by group, roles" and so-on.

So, if you really are seeing "certain groups can only see some fields", then it's a customisation you have not told us about. You'll need to work out which one that is, then go through your setup for it, probably while reading the documentation for it.

My best guess is that you have the Quisapps "field security" plugin , which is a rather good way to do this, but I'm not sure. You might be doing it with your own custom fields, the behaviours plugin, your own javascript hacks or some other plguin I've not yet run into. Start with https://marketplace.atlassian.com/plugins/com.quisapps.jira.jfs

KP11

We have views available only to certain user groups. I do nto see the Quisapps plugin. I believe the worflow routes developers to a certain screen based on their project

Nic Brough -Adaptavist-

> We have views available only to certain user groups

Right. So how *exactly* are you doing that? Jira simply does not support "hide field" or "make field only editable" by group or user so you have to be doing this with a plugin, code or some other hack, and you need to explain that before we can help you.

You've mentioned workflow, which implies you might be doing this with the standard workaround - you've got transitions that go through screens that allow the edit of issues for a limited set of people, in which case you need to look at the conditions on those transitions, in the workflow editor (and probably the screens they go through)

(Ok, Jira does actually let you control *edit* for reporter, assignee, fix version and due date with permissions. But no others, and there's certainly no "hide field" based on permissions, other than comments)

KP11

Under permissions we filter what groups can create issue. Under Project Permissions and Issue permissions. If a group does not have permissions they will go to a specific screen