Hi Greg,
Sorry to hear about this problem. If I understand your situation, it seems that your Jira 8.2.2 is not allowing you to remove that issue from the sprint as expected.
I have searched our public bug tracker, but I have not found an existing bug that matches your reported behavior here. Nor have I been able to recreate this specific behavior.
I would like to know more about your environment so that we can better troubleshoot this problem. Could you let me know the following?
- Have you tried this in different browsers, like Firefox, Chrome, etc?
- What exact steps are you following to remove the issue from the sprint? Are you using the backlog view to drag and drop the issue? Or has the sprint field been added to the issue screen allowing users to edit that field directly?
- I'd be interested to see if perhaps you can turn on the browser developer console and recreate this problem to see if the browser is logging any error messages in the process of removing the issue from the sprint. Chrome DevTools and Firefox: Opening the Web Console have steps on how to look at this.
- See if you can recreate this problem, and then immediately look into the $JIRAHOME/log/atlassian-jira.log file. I'd be interested to see if any kind of errors are being logged by Jira on the back end when this happens.
Perhaps with some more information we can better help troubleshoot this problem.
Regards,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.