High Issue Summary
**When in the Backlog view, moving a Done Issue from the current Sprint and dragging it down to the Backlog (or vice versa while it is still visible before refreshing the page) causes the browser to encounter an error.
Environment
(Optional - If Applicable)
- Jira Software 8.x
- SCRUM project
- Chrome, Firefox
- Backlog view with current Sprint on top
Steps to Reproduce
- Drag any complete Issue (not a Sub-task) from Sprint to Backlog and the browser will encounter an error after you acknowledge the Change in Scope.
- While the Issue is still on screen, you can drag it from Backlog to Sprint again and the same error will occur. If you refresh the screen, however, you cannot do this because the Issue is Done and it will no longer be populated in the backlog.
Expected Results
The Done Issue will move from Sprint to Backlog without encountering an error.
Actual Results
The browser encounters an error.
The Jira logs do not display an error. Only this is present in the atlassian-jira.log to indicate that an action occurred:
2019-07-24 14:47:28,616 SdOffThreadEventJobRunner:thread-2 DEBUG jiraadmin 887x868x1 1i7sqdg 0:0:0:0:0:0:0:1 /rest/greenhopper/1.0/sprint/rank [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.servicedesk.plugins.automation.servicedesk-automation-plugin] 2019-07-24 14:47:28,804 JIRA-INFORM-Thread-0 DEBUG jiraadmin 887x868x1 1i7sqdg 0:0:0:0:0:0:0:1 /rest/greenhopper/1.0/sprint/rank [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.jira.plugins.inform.event-plugin]
The below exception is thrown in the browser:
Notes
This is likely tied to the fact that Backlog isn't supposed to show Done Issues by default.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- resolves
-
JSWSERVER-19876 JS Exception while moving issues form active sprint to backlog
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|