How does the Issue Linking search work

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 viewing an issue, a user can link the issue to another issue (More > Link). During the issue linking process, the user can type a word and there will be some results showing (History Search & Current Search)

(Auto-migrated image: description temporarily unavailable)
(Auto-migrated image: description temporarily unavailable)

Solution

History Search

History search will return issues which the user have viewed recently. It refers to the filter issuekey in issueHistory() ORDER BY lastViewed DESC and contains the last 50-60 issues the user has viewed.

(Auto-migrated image: description temporarily unavailable)
(Auto-migrated image: description temporarily unavailable)

Current Search

This search will return issues currently based on the search currently in your issue navigator.

In my example above (searching the word email) you can see that the Current Search only shows issues from project JRA. That is because when I was linking the issue, the current search in my Issue Navigator was project = JRA. However, the History Search contains issues from JRA and JSD because they are within the past 50-60 issues which I have viewed recently.

Updated on April 1, 2025

Still need help?

The Atlassian Community is here for you.