-
Bug
-
Resolution: Fixed
-
Medium
-
6.0-OD-09, 6.3.4, 6.3.5
-
6
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Steps to produce:
- You need to perform Bulk operation for over 300 or 400 issues.
- For example 'Move Operation'for these 300 or 400 issues.
Actual Results
This will display the 'Down for Maintenance page' but the operation is still running in the background which makes the user confuse if JIRA is down or is till performing the operation.
- causes
-
JRASERVER-39940 Fix concurrency issue in bulk edit
- Closed
-
JSWSERVER-11255 Move issues between projects not working using Jira Agile board if the issue have subtasks
- Closed
- is duplicated by
-
JRASERVER-39296 JIRA Cloud bulk operation timeout due to webhook notifications
- Closed
- relates to
-
JRACLOUD-65874 Deleting large projects causes timeouts in JIRA Cloud
- Closed
-
JRACLOUD-32546 Bulk operation with over 300 issues time out and display Down for Maintenance page while is still running in the background
- Closed
-
JRACLOUD-65825 Bulk operation with over 300 issues
- Closed
-
JRACLOUD-66061 Changing issue security scheme causes timeout in ondemand
- Closed
-
JRASERVER-24875 Timeout message during issue cloning with many sub-tasks
- Closed
-
JRASERVER-39825 Make bulk operation progress page responsive
- Closed
-
JRASERVER-39826 Provide progress details of bulk operations
- Closed
-
JDEV-30296 Loading...