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

Date custom field in the epic and update using the children issuesc

Santiago Almeida

I have an item epic. The epic has children issues. The epic and the cildres issues have a field called Data de Início Real.

When the epic goes to a specific status (for example EXECUÇÃO) I need to update this field in the epic with the earliest value in these field (Data de Início Real), from children issues. Can you help me?

Accepted answers

Bill Sheboy

Hi @Santiago Almeida -- Welcome to the Atlassian Community!

What have you tried thus far to solve this need?

If you have a rule that is not working as expected, please post:

what version of Jira you are using (i.e., Cloud, Server, or Data Center),
an image of the complete rule, and
an image of the audit log details showing the rule execution.

Those will provide context for the community to offer suggestions.

If you have not yet started a rule, I encourage you to try to do so. Successfully using automation requires learning and experimentation.

To help you get started, your approach will depend upon your Jira version:

For Jira Cloud, you could use the Lookup Issues action to gather the child issues and find the earliest (i.e., minimum) date to use
For Jira Server / Data Center, the Lookup Issues action does not support custom fields yet. Instead, the rule will need to use the Send Web Request action to call the REST API for an issue search with JQL, and then get the minimum date from the web response.

Kind regards,
Bill

Santiago Almeida

The log is empty

All comments

Bill Sheboy

Hi @Santiago Almeida -- Welcome to the Atlassian Community!

What have you tried thus far to solve this need?

If you have a rule that is not working as expected, please post:

what version of Jira you are using (i.e., Cloud, Server, or Data Center),
an image of the complete rule, and
an image of the audit log details showing the rule execution.

Those will provide context for the community to offer suggestions.

If you have not yet started a rule, I encourage you to try to do so. Successfully using automation requires learning and experimentation.

To help you get started, your approach will depend upon your Jira version:

For Jira Cloud, you could use the Lookup Issues action to gather the child issues and find the earliest (i.e., minimum) date to use
For Jira Server / Data Center, the Lookup Issues action does not support custom fields yet. Instead, the rule will need to use the Send Web Request action to call the REST API for an issue search with JQL, and then get the minimum date from the web response.

Kind regards,
Bill

Santiago Almeida

Hi Bill,

I am using JIRA Cloud.
Thanks,

The rule i am doing is to prepare the solution.

Santiago Almeida

The log is empty

Bill Sheboy

Thanks for that information.

To use the {{lookupIssues}} smart value, your rule must first call that action, using JQL. An outline for your rule could be:

trigger: issue transitioned
condition: issue type equals Epic
action: lookup issues, with JQL to get the child issues for the epic
- parent = {{triggerIssue.key}}
smart value condition:
- first value: {{lookupIssues.size}}
- condition: greater than
- second value: 0
action: edit issue, to set your date field to
- {{lookupIssues.your field.min}}

Santiago Almeida

I am new here. Where I put the JQL?

Bill Sheboy

When you add the Lookup Issues action to your rule, you will see the location to enter the JQL.