Unexpected behavior seen when users make action on a tab it's result is seen on the other tab
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When using Jira in multiple browser tabs, users may experience unexpected behavior where actions from one tab seem to affect another. This is particularly evident when working on different projects in separate tabs. For instance, if a user switches from one tab where they were interacting with a specific project to another tab with a different project, they may still see behaviors or sessions relevant to the first project, especially if they click the Create button to create a new issue.
The shared session behavior in browsers is primarily designed for user convenience, allowing seamless interaction across multiple tabs without needing to re-authenticate or reload context continually. However, this can lead to confusion and errors in environments like Jira where users may work on different projects within the same browser session.
This issue arises due to the way web browsers handle sessions, particularly when multiple tabs are open. In a browser, session data is generally shared across all tabs. Jira, like many web applications, does not create isolated sessions for each tab because it relies on the browser's management of session data. This shared session model means that any change in session state in one tab (like authentication tokens, user preferences, or project-specific scripts) is immediately available to all other tabs. This design helps in maintaining continuity across the application but can lead to the aforementioned issues when working with multiple projects simultaneously in different tabs.
Solution
Manual Refresh: Refresh the tab after switching projects to ensure that the session updates to reflect the current project context.
Incognito Mode: Opening a new incognito or private window can also serve to isolate sessions temporarily.
Use Different Browsers: Consider using separate browser instances for working on different projects. This ensures complete session isolation.
Was this helpful?