Different results are displayed for different users with same roles and permissions for the JQL with sprint name conditions

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

Few users with same roles and permissions see different results while executing same JQL. 

Environment

8.13.x and later

Diagnosis

  • Here is a sample JQL, which was executed by two users. 

    1 project = PROJ1 AND sprint in openSprints() AND sprint != SPRINT1 AND sprint != SPRINT2 AND (issuetype = Story OR issuetype = Task AND "Story Points" is not EMPTY) ORDER BY summary ASC, Rank ASC
  • Some users see 0 issues while others see 100 issues. 

  • The issue is reproducible with safe mode as well, so it is confirmed no plugins are causing this issue. 

  • Confirmed sprint names are not duplicates.

Cause

  • Replaced Sprint name with SprintID in the JQL, which provided same results to all the users. Here is sample query: 

    1  project = PROJ1 AND sprint in openSprints() AND sprint != 1001 AND sprint != 1002 AND (issuetype = Story OR issuetype = Task AND "Story Points" is not EMPTY) ORDER BY summary ASC, Rank ASC

Solution

  • Modifying the JQL to use SprintId instead of sprint name resolved the issue. 

Updated on March 19, 2025

Still need help?

The Atlassian Community is here for you.