addedAfterSprintStart

The addedAfterSprintStart function identifies issues added after the sprint has already commenced. This function is crucial for agile teams to monitor and adapt to changes in their sprint commitments, offering benefits such as:

Enabling real-time tracking of scope creep or modifications within an active sprint, which is essential for maintaining sprint goals and expectations.
Providing insights into team adaptability and the dynamics of sprint planning, which can inform future sprint planning sessions and retrospective analyses.
Assisting in maintaining transparency and communication within teams by clearly delineating changes that occur during the sprint.

This function also considers issues that have been added to the sprint after the sprint start date, even if those issues were initially part of the sprint before it began.

CAUTION: Known Issue: addedAfterSprintStart

Issue Description: It is possible that the addedAfterSprintStart function may return inaccurate results when sprints are reopened.

Jira has a known limitation where, if a sprint is closed and then reopened, new changelog entries are created for all issues in the sprint using timestamps from the reopening event. Because the system relies on the latest changelog entry to determine when an issue was added to a sprint, this can affect the accuracy of tracking issue additions. While future improvements may be considered, there is currently no immediate fix due to the risk of impacting other scenarios.

Workaround: It is recommended to use explicit date-based queries together with the addedAfterSprintStart function to help address this Jira limitation.

Syntax and parameters

addedAfterSprintStart(Board, [Sprint])

Board: The name or ID of the agile board.
Sprint (Optional): The specific sprint to query. This can be the sprint name or ID. If using an ID, it should not be enclosed in quotes. If omitted, the function defaults to the current active sprint, unless there are multiple active sprints, in which case it is required to specify a particular sprint.

Examples:

Tracking scope changes in an active sprint:
For teams wanting to monitor what new issues have been added since the start of "Sprint 3" on the "EX Scrum Board":
1
```
issueFunction in addedAfterSprintStart("EX Scrum Board", "Sprint 3")
```
This query helps the team stay aware of any new commitments or changes in their current workload, allowing for more informed daily stand-ups and planning meetings.
Using Sprint ID to Specify the Sprint:
To specify a sprint by its ID for a more direct query without the need for quotes:
1
```
issueFunction in addedAfterSprintStart("EX Scrum Board", 30)
```
This approach is useful when working with dynamic board setups where sprint names might be reused or when integrating automated systems that track sprint changes by ID.To find the sprint ID:
1. Go to the board's backlog.
2. Right click the elipsis icon just above the sprint.
3. Copy the link, or URL, that looks similar to https://your-jira-instance.atlassian.net/rest/greenhopper/1.0/xboard/plan/sprints/actions?sprintId=30.
4. Go to the end of the link where you can retrieve the ID. In this example, the ID is 30.

Tip:Ensure accurate board and sprint linking: Remember that the sprint must be associated with the specified board; otherwise, the query will return no results.