We have discovered that when Bulk Changing the Status if there is required field that is already populated the bulk change is requiring it be selected and changed even though all the issues have the field populated. Is this working correctly or should this field not be required to be changes since all issues have it populated.
That's correct. Although the mandatory thing is incidental.
The point of bulk change is that you make the same change to all the issues you have selected. If you change a field, then the new value is supposed to go on to all the issues selected.
The mandatory flag is just making it a bit difficult for you - it's not historical, it only acts now. You've got at least one issue that has not had the field set, so JIRA is obeying what you've now told it and requiring a value for it. That's nothing to do with bulk edit really - it would do the same for each issue if you did them individually, but it is having an impact on what you're trying to do with bulk edit.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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