-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Low
-
None
-
Affects Version/s: 9.4.12, 10.3.0
-
Component/s: Issue - Actions, Project - Issues
-
None
-
9.04
-
Severity 3 - Minor
Issue Summary
When moving an Epic with 11 subtasks from one project to another, one of the subtasks does not move to the target project.
This is reproducible on Data Center: Yes
Steps to Reproduce
- Create two projects (ProjectA and ProjectB)
- Create an Epic under ProjectA
- Create 11 subtasks under the epic
- Move the Epic to ProjectB
Expected Results
All subtasks moves to the projectB
Actual Results
11th subtask does not move to the ProjectB
- The problem occurs only when epic has 11 Subtasks
- Tested with 10 or 12 subtasks and it works fine
The below message maybe thrown in the atlassian-jira.log file:
/secure/views/bulkedit/BulkOperationFinish.jspa; user: admin WARN admin 749x2461x1 5qups8 172.29.216.176,10.224.217.132 /secure/views/bulkedit/BulkOperationFinish.jspa [c.a.j.w.a.issue.bulkedit.BulkOperationProgress] Bulk edit bean unexpectedly null. Perhaps session was lost (e.g. when URL used is different to base URL in General Configuration)?
Workaround
After moving the Epic fromProjectA to ProjectB, move same the Epic from ProjectB to ProjectB
- duplicates
-
JRASERVER-78403 Moving a Jira issue with 11 sub-tasks leaves one sub-task behind
-
- Closed
-