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

send email when the value of a field changes

José Manuel Martín Márquez

I'm using Jira Product Discovery and i want to send an email when the value of the field "Estimated End Date" changes, so I created this Automation

But when the Estimated End Date value changes, the rule does not trigger. the value of this field is not set manually by the user, but is automatically filled in from the latest end date of all delivery tickets that are linked.

How could i resolve this problem? imagen (5).png imagen (6).png

Accepted answers

All comments

Rik de Valk (Brainboss)

Hi @José Manuel Martín Márquez ,

And welcome to the community!

In your first screenshot, you see the Rule details. At the bottom there is a checkbox "Check to allow other rule actions to trigger this rule".

Once you select that and save your rule, it will also trigger on automatic changes to the field value.

Have a nice day!

Rik

José Manuel Martín Márquez

Thanks for your answer Rik. Yes, after adding this question I tried selecting that checkbox but the rule still doesn't launch when the ‘Estimated End date’ value changes.

Boyan Iliev_7n6lmk

Hi @José Manuel Martín Márquez , the audit log can provide some clues on what is happening. Can you open it after an estimated end date changes and confirm if the rule executed at all? Is there an entry with an error, or maybe "NO ACTIONS PERFORMED", or there are no executions at all?

You can also try a manual change of the date and again review the audit log, to compare the outcome.

If the rule did not execute at all, I would assume something general is misconfigured. Maybe its on the wrong project, or you have multiple fields with similar names. Or as you suggested, "Value changed" does not pick up automatically filled values.

If the rule did execute - go to "show more" to review what each step of the automation did. Who triggered it - hopefully this automatic filling, did it pass the status check, etc.

Based on the above, we can definitely look for next steps.

José Manuel Martín Márquez

Thanks @Boyan Iliev

As you can see, after chaging the "end date" field for the Epic, the "Estimated End date" value changes well but the rule does not trigger

Captura de pantalla 2024-12-20 085342.png

I cannot change the "Estimated End date" value manually as it's configured to autofill dates. There is no other field with the same name and the project is the correct one.

I guess "Value changed" does not pick up automatically filled values but in that case the checkbox "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule" makes no sense

Boyan Iliev_7n6lmk

This is probably the easier thing to troubleshoot, although the outcome might not be what you like. Here are few ideas:

Can you double-check the "Field value change" trigger setup? Can you try to play with these to get the rule to pick-up the change:
1. What is set for "Change Type"
2. Did you set anything for "For"?
Can you disable the auto filling and do a manual change, just to confirm this hypothesis? Of course - turn on the automation after that to avid issues in your project
Can you double-check that the rule triggers on a different date type field change. Just to be sure its not some sort of restriction?
Are there other things that change together with the Estimated End Date? Maybe you can use one of them to trigger the rule?

José Manuel Martín Márquez

Thanks again @Boyan Iliev

1- Change type is set to "Any changes to the field value" and there is no "For"

2- The rule trigger if I disable autofilling, so I guess i was right and "Value changed" does not pick up automatically filled values

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-cloud