Community
Products
Jira
Questions
Bulk Operations Tool - Edit Screen 3 of 4 Change pre-selections

Bulk Operations Tool - Edit Screen 3 of 4 Change pre-selections

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.

1 answer

1 accepted

0 votes

Answer accepted

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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'.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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