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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi. From the issue view I apply a filter and start a bulk change operation to transition a group of issues from one status to another.
When I click "Next"-button to perform the operation I get an internal server error.
"Something went wrong
Try reloading the page, then check our Statuspage for any current outages. If there are no relevant outages, create a support request so we can help you out.
If you create a request, include the following so we can help you as fast as possible:
In addition I get a log reference. Anywhere I can read more information based on this log reference?
This is the bulk change operation triggered .../secure/views/bulkedit/BulkWorkflowTransitionDetails.jspa
Hope someone can help or point me in the right direction here. Thanks.
It's always good to check the Atlassian Status Page when odd things like this happen, just in case there is a known incident in progress (in which case "try it later" is suggested).
I looked back to early May 2021 for Jira and didn't see anything related.
For others experiencing something like this, one suggestion is to try to manually transition just one issue (or a few of them), to ensure that the workflow and project configuration is working as expected.
You're likely to get a better user error when manually updating one issue. Examples here include misconfigured workflows (esp. conditions and validators), transition screens, and even field visibility problems.
I'm assuming, since it's been a while, that you've gotten past this problem. Feel free to share back what worked for you. Best wishes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.