Sprint Designation is different

David Cox
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 4, 2023

I noticed that a jql statement that my sprint # is actually traced in the background as a different sequential number (e.g., Sprint 20 (basic) is also Sprint 124 (jql)). 

I created the search via basic.

I work in a large organization and the sequential numbers are in order by multiple project sprints.

In order to create a jql query, I need to know the corresponding background #.  How do I find it - it doesn't work quoting the end-user sprint #

 

1 answer

1 accepted

0 votes
Answer accepted
Florian Bonniec
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 4, 2023

Hi @David Cox 

 

Not sure to understand the issue. Are you saying that Sprint 20 is also Sprint 124 ?

From a general matter it's not a good idea to name sprint with Sprint 1, 2 etc... as in the Sprint field any Sprint will be displayed, there is the risk that someone selected the wrong Sprint in the field if it's available in any Edit screen in any porject.

The naming convention should include the team name or product name that make sure the Sprint name is unique across multiple boards.

 

Regards

David Cox
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 4, 2023

Obviously, I wasn't clear enough.  Here are the specifics:

The Sprint is called:  "BRAV Sprint 30"...BRAV being the abbreviation for the Project called BRAVO.  When I switched over and looked at the jql statement on a filter that I created via basic, the sprint is = 124, not BRAV Sprint 30.

Florian Bonniec
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 4, 2023

Ya that's the expected behaviour. It's replacing the Sprint name by the Sprint ID. But using JQl it will autocomplete and suggest Sprints using their name, it's just when selecting the value that it will switch to the ID for you, so no need to have the ID in that case.

cloudjqlsprint.png

The issue come when you have a filter and you do not recall what Sprint it's related to. You can name it in the filter at creation or use the rest api to get the name of the sprint from the ID.

https://developer.atlassian.com/cloud/jira/software/rest/api-group-sprint/#api-rest-agile-1-0-sprint-sprintid-get

Once log into JIRA you can type this in the browser url then hit enter.

<YOUR_DOMAIN>.atlassian.net/rest/agile/1.0/sprint/<SprintID>

It will return the information about the Sprint

{"id":1,"self":"https://XXXXXX.atlassian.net/rest/agile/1.0/sprint/1","state":"future","name":"sdfsdf Sprint 1","createdDate":"2023-10-04T18:41:30.631Z","originBoardId":3}

Regards

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events