-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Low
-
Component/s: Work Item - Bulk Updates
-
16
-
Severity 3 - Minor
-
1
Summary
A session timeout error is shown when bulk editing sub-tasks. It happens only when selecting bulk edit by clicking on the (...) button above the sub-tasks list inside a parent issue (see screenshot below).
Your session timed out while you were in the process of selecting issues to perform a bulk operation on. This means that we have lost the information that we collected thus far from the wizard. You will need to try the bulk operation again from the start. Sorry for the inconvenience.
Environment
There is no specific environment
Steps to Reproduce
- Go to an issue with sub-tsks
- Above the list of sub-tasks click on (...) > Bulk Operation
- Select all sub-tasks and click on next
Expected Results
The page to select the bulk operation should appear
Actual Results
The below exception is thrown in the UI
Your session timed out while you were in the process of selecting issues to perform a bulk operation on. This means that we have lost the information that we collected thus far from the wizard. You will need to try the bulk operation again from the start. Sorry for the inconvenience.
This one appears on jlog
/secure/views/bulkedit/BulkMigrateSetFields.jspa [c.a.j.w.a.issue.bulkedit.BulkMigrate] Bulk edit bean unexpectedly null. Perhaps session was lost (e.g. when URL used is different to base URL in General Configuration)?
This appears on aalog
"POST /rest/webResources/1.0/resources HTTP/1.0" 200 1039 37579 "https://xxx.atlassian.net/secure/views/bulkedit/SessionTimeoutMessage.jspa?timeout-cause=bulk.operation.session.timeout.message" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"
Notes
(Optional - If Necessary)
Workaround
- Go to Issues > Search for issues
- Search for parent issue (parent = TEST-1), it’ll list all sub-tasks
- Click on (...) > Bulk edit
- mentioned in
-
Page Loading...