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 Operations Tool - Edit Screen 3 of 4 Change pre-selections

martin.abbott

What determines whether a field is preselected (tickbox) for change on Screen 3 of 4 in the Bulk edit operation ?

We have a few 'Database Customfields' a long way down on the screen which are mysteriously pre-selected (with blank vallues). This means that super users are often caught by this and inadvertently blank out existing values.

Accepted answers

Nic Brough -Adaptavist-

It's hard to say, as the database custom fields are not Atlassian fields, and hence have their own behaviours. I suspect it's the field trying to read the database for many issues.

All comments

Nic Brough -Adaptavist-

It's hard to say, as the database custom fields are not Atlassian fields, and hence have their own behaviours. I suspect it's the field trying to read the database for many issues.

martin.abbott

Frustrating, but I think you right. Looks as though the 3rd party 'database customfield' doesn't sit well in the Bulk operations page. It's running in a many issue context and maybe it is only designed for 'CREATE' or single 'UPDATE'.

Nic Brough -Adaptavist-

That's my feeling too, as the field is dragging stuff from a remote database, maybe it's making lots of calls and getting confused when you go to bulk-edit.

Christian Schlaefcke_9pmuqe

Hi Martin,

are you still encountering this issue? I am running into this with 7.9.2 JIRA (will be updated shortly) and wonder if this will vanish with the latest JIRA version (e.g. 8.5.x).

We use nFeed/Elements Connect by the way. Maybe I am going to contact Elements on this...

Thank you & Best regards,

Christian

Welcome!

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

Quick Links

Find more posts tagged with

jira-core