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; } } }

How to set start date on parent ticket if there are multiple subtasks.

Pete Jaworski

I would like to set the Start Date on a Parent Issue (Story and Epic) when the FIRST story or subtask gets moved into Development.

I have an issue where every time a subtask or Story moves into Development the Start Date Changes on the Epic or Story Level.

There are times where the subtask are in different stages of the workflow, but the start date keep changing every time that it may go in and out of a status. See Example screenshots.

Example Story with Subtasks.png Automation Rule Start Date - Story.png

Accepted answers

Trudy P Claspill

Hello @Pete Jaworski

You will need to add Condition(s) to check if there is more than one "child" issue in the "In Development" status and only change the Start Date of the parent when there is only one "child" issue in that Status.

Something like this should work:

Screen Shot 2023-07-24 at 1.45.41 PM.png

All comments

Trudy P Claspill

Hello @Pete Jaworski

Something like this should work:

Screen Shot 2023-07-24 at 1.45.41 PM.png

Pete Jaworski

@Trudy P Claspill @hank you for the quick response. Should I add this to my Existing Rule when I not only transition subtasks to "In Development" and update the User Story status, also the start date?

Also, for some reason the JQL Lookup issues is not able to validate the query. Is that look correct?

parent = {{issue.key}} and status="In Development"

Screenshot 2023-07-24 at 5.03.43 PM.png

Trudy P Claspill

In an Automation Rule the Validate Query option will not work when the query includes smart values, because the smart values cannot be evaluated except when the rule is executing.

As per your latest image the parent's Start date will updated only when a subtasks transitions to In Development and that is the only subtask in that status. The change of the parent's Status will not be affected by the change.

I do wonder though if you have the rule set the way you really want it for changing the parent's Status.

If any subtask is transitions to "In Development" from one of the specified statuses then the parent issue will also be transitioned to "In Development" regardless of what status that parent is in currently.

1. You might want to add a check to confirm that the parent's Status is not already "In Development".

2. In addition, do you want the parent to try to transition to "In Development" regardless of its current status? Are there any statuses from which the transition to "In Development is not possible? If so you might want to consider other current status values to check for on the parent in #1.

3. If you do opt to add a condition to check the parent's status, then I would recommend having two separate branches; one for updating the parent's Status and the other for updating the parent's Start date. If you keep them in the same branch, then the first condition that fails will cause the branch to exit without proceeding farther to assess any additional conditions.

Pete Jaworski

Gotcha.

What I really want is:

1. If any subtask is transitions to "In Development" from one of the specified statuses then the parent issue will also be transitioned to "In Development" regardless of what status that parent is in currently.

2. Then, when the Parent is "In Development" status, add the current date as the start date.

How would these two rules look like? My main issue im trying the solve is the start date updating everytime a new subtask, under the parent, moves to "In development", its messing up my start date.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud