You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.
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.
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,