BUG: Bulkedit with dual browser tabs will screw up the cache

[Anders Bern]

Imagine you have two tabs with two different  queries. A and B.
Query A in tab left, Query B in tab right.
Now press search on tab left - this places the response of Query A in cache.
Now go to tab right and do bulk update. and try to catch B.
it will take the WRONG response(meaning A) but the number of cases from the right tab's response B.....

and if this wasn't bad when going "oh shit - cancel is a good idea at this time". the last preformed query (still A) will overwrite the tab on the right.
The only way to save your xxx is to back up the browser.

Reproduced on chrome and edge and in incognito.

Wanted state: When pressing bulkedit THAT tabs query needs to be refreshed. Before heading into bulk edit.

[Nic Brough -Adaptavist-]

There's no way to do this, the browsers tabs are not aware of what each one is doing.

[Anders Bern]

From a enduser perspective i'd disagree.  it clearly appears as if they are all and one and messes query responses up btw tabs. - but OK - ill give it a shot with different Browsers windows as well.
Tabs are then to be considered as fake-tabs/fake separations. :D

[Anders Bern]

seems awfully "alike" situation - https://community.atlassian.com/t5/Jira-Software-questions/BUG-Jira-Issue-Issue-created-in-wrong-project-multiple-projects/qaq-p/820874

[Anders Bern]

https://jira.atlassian.com/browse/JRASERVER-39420

https://jira.atlassian.com/browse/JRACLOUD-69274%C2%A0

https://community.atlassian.com/t5/Jira-Software-questions/BUG-Jira-Issue-Issue-created-in-wrong-project-multiple-projects/qaq-p/820874

Attaching related matters.
doing "bulk edit" ought to preform a re-search of current tab to protect the intention of the bulk. (almost screwed things up today)