Scheduled actions - Agile sprint scope

The following use cases use JQL Search Extensions (JSE) filters based on Agile sprint functions to set the scope for scheduled actions in JMWE.

On this page: 1 Problem to solve 2 Solution 3 Create a scheduled action that sends a daily email with a list of issues added to the current sprint after the start date 4 Create a scheduled action that sends an email every week with a list of issues to review before the next sprint starts

On this page: 1 Problem to solve 2 Solution 3 Create a scheduled action that sends a daily email with a list of issues added to the current sprint after the start date 4 Create a scheduled action that sends an email every week with a list of issues to review before the next sprint starts

Problem to solve

Agile teams often face challenges managing workload visibility throughout and between sprints. New issues added after a sprint starts can disrupt capacity and workload management, while incomplete preparation for upcoming sprints can introduce delays and reduce predictability. This dual challenge impacts effective sprint planning, resource allocation, and prioritization, creating a lack of visibility into what tasks have been added mid-sprint and what needs attention before the next sprint begins.

Solution

Schedule email notifications to highlight scope creep and ensure issues are prioritized ahead of time for upcoming sprints.

Create a scheduled action that sends a daily email with a list of issues added to the current sprint after the start date

JSE function	`addedToSprintAfterStart()`
JMWE scheduled action	`Every day at 12:0 UTC`
JMWE action	Email Issues
Method	In JQL Extended Search, perform a search for issues added to a sprint after the start, for example: `issue in addedToSprintAfterStart(ACME)` Click Save the query as a filter. Enter a name for the filter, then click Save. For this example, the filter is called `Issues added after sprint start`. In JMWE, create or edit a scheduled action to occur `daily at 12:00 UTC`. Under IF SCOPE, click Select Target Issues. In the JQL Expression input box, enter the filter name, for example, `filter="Issues added after sprint start"`. Add the Email issues post function and configure the recipients and message subject. Save the action. Now, every day, the team lead will receive an email with a list of issues added to a sprint after the start date.

Create a scheduled action that sends an email every week with a list of issues to review before the next sprint starts

JSE keyword	`nextSprint ()`
JMWE scheduled action	`Every week on Tuesday at 08:30 UTC`
JMWE action	Email Issues
Method	In JQL Extended Search, perform a search for child issues matching a given query, for example: `issue in nextSprint(15)` Click Save the query as a filter. Enter a name for the filter, then click Save. For this example, the filter is called `Issues in next sprint`. In JMWE, create or edit a scheduled action to occur `weekly on a Tuesday at 08:30 UTC.` Under IF SCOPE, click Select Target Issues. In the JQL Expression input box, enter the filter name, for example, `filter="Issues in next sprint"`. Add the Email issues post function and configure the recipients and message subject. Save the action. Now, every week, the team PM will receive an email with a list of issues planned for the next sprint.