Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
4.3.3, 6.4.11, 7.0.0, 7.6.15, 9.4.6, 9.10.0
-
None
-
4.03
-
17
-
Severity 1 - Critical
-
9
-
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
When bulk editing based off of a filter, it will use the issues from the last filter that was run (ie. Current search) rather than the issues on the page that is being bulk edited.
Steps to Reproduce
- Run a search
- Navigate to a different tab and run another search.
- Navigate back to the first tab and click on (Tools > Bulk Change)
OR
- Run a search
- Navigate to a different tab and delete an issue
- Navigate back to the first tab and click on (Tools > Bulk Change)
Expected Results
The issues listed on the Bulk Edit match the search from the first tab.
Actual Results
The issues listed on the Bulk Edit are shown according to the search performed in the second tab.
Impact
Users can not perceive that the selection is showing different results and bulk edit the results for updates or deletion, causing data loss.
Notes
- Notice that the issues pulled into the bulk edit screen are the issues from the search in the other tab. However, the results are limited to the number of issues found on the first tab, which adds to the confusion and causes it to go unnoticed.
- This also has impact if you just delete an issue in another tab. When deleting an issue, you search will automatically be changed to the project default search below
project = "KEY" AND resolution = Unresolved ORDER BY priority DESC, updated DESC
- This causes the Bulk Change to use the project default search and users will end up updating/deleting a complete set of incorrect issues.
Workaround
Currently, there's no workaround for that.
Attachments
Issue Links
- is duplicated by
-
JRASERVER-36286 Bulk Change uses filter from navigation context instead of the one displayed in the UI
- Closed
-
JRASERVER-24678 Loading issue navigator in a separate tab causes bulk operation to populate with the wrong issues
- Closed
-
JRASERVER-60094 "Bulk Operations Error" when performing bulk operations in more than one tab
- Closed
-
JRASERVER-60555 Bulk change selects results from last query in session, not results from query on page
- Closed
-
JRASERVER-64916 Bulk Edit takes results of second tab instead of initial tab where the edit is initiated.
- Closed
-
JRASERVER-61804 Bulk selection (bulk change) is wrong when 2nd search is performed in another tab/window
- Gathering Impact
-
JRASERVER-16066 bulk link on issue list works on current list and not with the one displayed
- Closed
-
JRASERVER-66311 Bulk change to use JQL from page that it is accessed from
- Gathering Interest
- is related to
-
JRASERVER-39420 When doing Bulk Change, JIRA uses the "Current Search" instead of the filter on the page
- Closed
-
JRASERVER-14442 Support more than one 'active'/simultaneous Issue filter in a session
- Closed
- relates to
-
JRACLOUD-62637 Bulk Edit retrieving wrong issues
- Closed
- mentioned in
-
Page Loading...