Can we have JQL functions created for openSprintStartDate() and openSprintEndDate() ?

[Arijit Mandal]

I have some filters which are based on issue created date within the range of open sprint start date and end date. I can not rely on sprint field due to other challenges, hence it has to be by Created Date only. Some JQL functions like openSprintStartDate() and openSprintEndDate() would have been very handy and will save my effort for modifying the query every sprint.

[Trudy Claspill]

Hello @Arijit Mandal 

Welcome to the Atlassian community.

Can you provide an example of how you would anticipate using such functions in a JQL query?

There may be a third party app that can fulfill your needs, but we need to understand your use case to make suggestions.

Note also that this is a community of Atlassian users. This is not the forum for submitting a product suggestion.

[Arijit Mandal]

I have a query to find all bugs reported within a span of a sprint. I can't use the Sprint field as it is used to denote when the Bug is targeted for fix, not when it was opened. I can add another customer field to track it separately or I can use a JQL something like below

project = <project> AND issuetype = Bug AND created >= <sprint start date> AND created <= <sprint end date> 

In this query I'll have to change the sprint start date and end date for each sprint. Rather than doing that, I was wondering if something like this is available 

project = <project> AND issuetype = Bug AND created >= openSprintStartDate() AND created <= openSprintEndDate()

Then the query becomes dynamic and it'll always return the bugs opened within currently open or active sprint.

[Trudy Claspill]

Hello @Arijit Mandal 

Thank you for that additional information.

There currently is not any function that does what you want in a single query like you have described.

As there can be many open/active Sprints across a Jira instance, how would you anticipate that Jira would determine which one you wanted to use in this query? Are you expecting it to dynamically determine that by looking at the sprints associated to each issue that otherwise fall within the scope of your filter?

I'm not sure, without additional research, if there is a function that you can use to identify the open/active sprint to which an issue is currently assigned.