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.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs