An issue has been reported regarding the OpenSprints() function within Jira Query Language (JQL). This article addresses the problem and provides a straightforward solution for users experiencing difficulties.
A user, Sharon Youmans, reported that the OpenSprints() function was no longer functioning correctly. Initial investigation suggested a potential replacement of the “Sprint” field within Jira. Adam Rypel from MoroSystems confirmed the function was working as expected for him. The root cause appeared to be the creation of a duplicate field named “Sprint” within Sharon’s Jira instance, leading to JQL confusion.
The recommended resolution involves renaming the newly created “Sprint” field to avoid conflicts. Alternatively, a temporary workaround is to select one of the “Sprint” fields within the JQL query, as suggested by Adam Rypel. Sharon was unable to locate the new custom field through a global search, highlighting the need for more precise field identification. Selecting the sprint value from the dropdown menu also failed to populate any values.
This issue has been resolved by identifying and renaming the duplicate field, ensuring JQL correctly references the intended “Sprint” data within the OpenSprints() function.
Source: https://community.atlassian.com/forums/Jira-questions/OpenSprints-function-does-not-work-in-JQL-Jira-anymore/qaq-p/2606463
Leave a Reply