JIRA Requires Duplicate Logins when Selecting Items from a Gadget or the Activity Stream Due to Server Base URL

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

Symptoms

JIRA seems to require duplicate logins when clicking on items in the Activity Stream.

Diagnosis

Check the server base URL in Configuring JIRA Options, and confirm that it matches the Server Base URL rendered in the Activity Stream Gadget.

Cause

There is a mismatch in the server base URL from how the activity stream gadget was configured and the server. It's possible that a user is logging in using an alias for JIRA.

Solution

Resolution

Make sure the user is logging in from the standard server base URL, not an alias.

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.