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

Bulk editing fields

Karie Kelly1

Why is the bulk editing displaying field options that are not on the screens? For example, we have hidden the Epic/Theme field from our screens and it doesn't appear when editing an issue; however, it does appear as an option for bulk editing.

How do we make the bulk editing options the same as the screen to avoid users accidentally using a field that they cannot see/use otherwise?

Accepted answers

Ramiro P

Hi,

I believe that inside the bulk edit you can't choose what fields should show. By default it brings any field that can be edited. I see the same thing. I guess you could create a feature request in jira.atlassian.com

In the meanwhile, I recommend to enable this bulk edit only for 'experienced' users.

All comments

Ramiro P

Hi,

In the meanwhile, I recommend to enable this bulk edit only for 'experienced' users.

Karie Kelly1

I'll definitely add a feature request. It seems odd that the bulk edit doesn't align with the same screen definitions that we have taken the time to setup or at least define what fields can be used for bulk editing to avoid confusion and orphaned data

Ramiro P

It really seems odd, I never tought about it. Maybe it is because you can select a lot of issues that are different issue types, so it's difficult to map the fields from the screens. I'm sure it will be a lot of work

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-cloud