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

Hide/Remove fields in 'Order by Priority' dropdown-menu

Luca Edler

Hello community,

I got several projects in our Jira Server installation. In Each of these projects, I want just the fields defined in the unique field configuration to be displayed in the 'Order by Priority' menu.

At the moment the situation is, that every custom field of every project is searchable in any project.

To make the fields invisble/unsearchable, I created custom field configurations (and schemes) for each of the projects and have set the fields, I don't want to be shown, to status 'hide'.

Maybe this already is the point, because they're just hidden but not removed, but I haven't found a way to delete them.

Any idea?

Kind regards

Luca

Accepted answers

Luca Edler

Ok, I found a way!

Administration

-> Issues

-> Custom fields

-> choose settings button on the very right of the field you want to change

-> configure

-> click on "Edit Configuration" next to 'Applicable contexts for scheme:'

-> under "Choose applicable context" choose "Apply to issues under selected projects" and

-> select (multiple projects by holding strg) just the Projects, where you want the fields to be visible and searchable.

Edit: Read my comments below, they are almost more important than this post here.

All comments

Luca Edler

Ok, I found a way!

Administration

-> Issues

-> Custom fields

-> choose settings button on the very right of the field you want to change

-> configure

-> click on "Edit Configuration" next to 'Applicable contexts for scheme:'

-> under "Choose applicable context" choose "Apply to issues under selected projects" and

-> select (multiple projects by holding strg) just the Projects, where you want the fields to be visible and searchable.

Edit: Read my comments below, they are almost more important than this post here.

Luca Edler

Still buggy.

I did the above steps and created for testing purposes a new testuser. This testuser was added to the same groups, the people within the project, who can see all those fields that should be hidden, are part of. So, the permissions should be the same. I checked the project roles too and if there are single users added in the permission scheme or the project role section.

At the moment, I can't see any difference in terms of permissions between my testuser and the people in the project.

But:

The people in the Group can still see any Custom Fields when they click on "Order by" above the issue-table. But clicking on "View all issues and filters" -> "More" -> "All criteria", there are just the "allowed" ones and underneath "excluding ... hidden".

The testuser with the same permissions can't see neither the fields in the "Order by"-dropdown, nor the excluded hidden ones.

So why is there a difference between the users? And why can the people see the fields in the list but not in the other menu?

Luca Edler

Finally got the solution.

It seems everything I've written before is right so far. It's just a problem in understanding by me what's shown in Jira.

Clicking within a project in the issues-menu the "Order by"-Button, you will see all fields of all projects, YOU are part of. That means, everyone sees there a different amount of fields!

I think it's kind of confusing, because one could think, everyone f.e. customers with Jira-access can see all those fields.

Welcome!

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

Quick Links

Find more posts tagged with

server

custom-field

jira

jira-server

hide

remove