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

Start dates/Due dates not inherited in child tickets via automation

Aristos Smirniotis_su7oo2

Hey Jira community!

I recently made an automation rule that is supposed to allow a child ticket to inherit field data from a parent ticket.
All the fields in the rule auto-populate except the start date and end date. It always comes out blank in the child ticket.

Ive attached a screenshot of the rule. What do I need to do to fix this? Thank you! Screenshot 2024-12-13 at 11.11.36 AM.png

Accepted answers

All comments

Manoj Kumar Gangwar

Hi @Aristos Smirniotis

Please verify the date fields, are you using the same fields which are used in the parent? Please share the screenshot of parent issue fields.

Please check if there are multiple fields available with the same name.

Aristos Smirniotis_su7oo2

Screenshot 2024-12-13 at 12.54.57 PM.png Screenshot 2024-12-13 at 12.55.30 PM.png

Aristos Smirniotis_su7oo2

@Manoj Kumar Gangwar Hey Manoj,
Thank you for your help.

Ive attached the screenshot of both task and sub task outline and have verified that they are using the same fields as in the automation rule.

Aristos Smirniotis_su7oo2

There are no other start date/due dates fields in the context for each outline

Bill Sheboy

Hi @Aristos Smirniotis

When an automation rule accesses the smart values for the connected issues, it only loads a few of their fields, such as Key, Summary, Status, etc. These connected issues, smart values include at least:

{{issue.parent}}
{{issue.subtasks}}
{{issue.issuelinks}}

If instead the rule pulled in all of the data for those issues, you could easily imagine their connected issues would pull in others, in an ever increasing tree of potentially thousands of issues!

When you want other than the basic fields in the connected issues, use the Lookup Issues action with JQL to load the data for those issues, such as the parent, and then use the {{lookupIssues}} smart value in the rule.

Kind regards,
Bill

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management