i am creating an automation to send myself everyweek an update on all WIP issues.
in the email i have the details of each of said issues including summary, description, parent, status, and comments history.
I am trying to get additional history information for status.name, assignee and duedate but those are not working.
For comments i used this parsing:
{{#comments}}
Update of {{created.format("dd-MMM-YYYY")}} by {{author.displayName}}: {{body}}
{{/comments}}
which works fine.
I tried with to replicate the same for these other fields but nothing is working and all come up empty.
Examples:
A.
{{#status.name.fieldChange}}
Update of {{created.format("dd-MMM-YYYY")}} From: {{fromString}} to {{toString}}
{{/status.name.fieldChange}}
B.
{{#status.name.changelog}}
Update of {{created.format("dd-MMM-YYYY")}} From: {{fromString}} to {{toString}}
{{/status.name.changelog}}
can you help?
Hi @Francisco Ochoa Di Iorio -- Welcome to the Atlassian Community!
For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
The changelog smart values only apply when:
A rule cannot directly view the changes over time with smart values. It is possible to call the REST API functions with the Send Web Request to view the complete issue history, although that would need to be loaded in pages and filtered to get the entries for your field, such as Status.
Perhaps if you explain what you are trying to view for the Status field changes the community can suggest other ideas.
Kind regards,
Bill
Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.
Learn more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.