Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
Description
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Create 2 filters. Have one find 1 set of tickets and have the second find another set of tickets.
Now one after the other, load them in separate tabs. To make it really obvious, open the first, wait until it fully loads, then open the second.
Now, start a bulk change on the first one that loaded. You will see that filter 1 is actually displaying! This can be really confusing if you haven't already experienced it! It defies sense.
I didn't dare see on my local machine which set ends up being used for the bulk operation...but I wouldn't be surprised if the wrong set gets used...it might explain why bulk operations in the past for me went awry.
Attachments
Issue Links
- duplicates
-
JRACLOUD-39420 When doing Bulk Change, JIRA uses the "Current Search" instead of the filter on the page
- Closed
- is related to
-
JRASERVER-43733 Bulk change on filters step on each other
- Closed