nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is the JQL query to find issues in a sprint at the start?

Sandy Greenberg

To find issues in a sprint I can use "project = "xxxxx" and sprint = 81998" or "project = "xxxxx" and sprint = openSprints()".

However, this would be a dynamic list. As issues were added or de-scoped during a sprint the results list will change. I need a static list that shows me the issues in a sprint when it was started.

Any ideas?

Accepted answers

All comments

Hello @Sandy Greenberg

Script runner gives you the function

addedAfterSprintStart

issueFunction in addedAfterSprintStart("Sample Scrum Board", "Sample Sprint 3")

Since you want exact list at the start of sprint then you can write your JQL like

Sprint = "Sample sprint 3" and issueFunction NOT in addedAfterSprintStart("Sample Scrum Board", "Sample Sprint 3")

Thus you should have the issues which have the sprint field as "Sample sprint 3" and were not added after sprint start which would imply that they were present at the start of the sprint.

Hey Sandy,

You should be able to use the Sprint Report to view this information.

You can fund this on the board where the Sprint was started under reports.

Hope this helps,

Tyler

Sandy Greenberg

Thanks, but our installation doesn't have ScriptRunner.

Sandy Greenberg

Yeah, the Sprint Reports are good but we want a JIRA list on a Confluence page.

Without the help of an addon, it would only be possible to adopt a procedure to produce the desired result.

If users in your organisation added a label to all issues in a sprint on starting it -through a bulk change operation- then you would be able to retrieve them at a later stage.

Sandy Greenberg

The procedure we're trying is to export the list of stories to Excel at the start of the sprint to keep an static record. Adding a label is a good idea though.

Jens Christian Hansen

I do: sprint = "Sprint 1.1" AND type in (task, bug, story) AND NOT issueFunction in addedAfterSprintStart("AEOI - Backlog", "Sprint 1.1") OR issueFunction in removedAfterSprintStart("AEOI - Backlog", "Sprint 1.1")

it also captures the issues removed after sprint start. Problem is:

If an issue is added before but also removed before then added anuway in sprint it is shown as part of commitment, witch it was actually not.

Anandan Subramani

Labeling, as suggested by Pulgar, is an easy and good solution. Add all issues with a Label default value representing static issues created at the start of a project. Remove the default value after the creation of static issues.

I don't know whether there is a Jira feature that can be set either on or off to prevent an issue from being deleted after the start of Sprint or whether an issue can be marked as deleted but stays in the backlog forever.

I am new to Jira. Four years have passed since the query was raised, and this may be an outdated solution.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

jql

atl-gruland