I apologize in advance for the vagueness of this but I am currently at a loss on what is triggering this for us in the first place.
We have a frequently used transition by one of our QA leads when assigning out issues to the team. Typically they are looking at a list of issues, possibly editing them then triggering this transition where they chose who to assign it to. Then they use the navigation arrow to go to the next issue in the list and repeat. Occasionally this transition will display an error that is only up for a few seconds that says "Comment body can not be empty." After it goes away, they are viewing the bug they just changed but no longer have the navigation arrows and have to go back to the list to keep going.
There is no validator on this transition that would require a comment. Some times you might get through several issues before it happens again.
I do not even know where to start to try and figure out this problem. Has anyone else seen this?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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