Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

In an automation rule I need to set the due date 3 months later the ticket had been created.

Sofia Grunspan
Contributor
June 19, 2023

I'm working in a automation rule and I need to set the due date 3 months after the creation date of the ticket.

For example if the ticket was created 1 January, the due date would be 1 April.

How can I set that with smart values? 

Thanks

1 answer

1 accepted

4 votes
Answer accepted
Mark Segall
Community Champion
June 19, 2023

Hi @Sofia Grunspan - You should be able to do it like this:

{{issue.created.plusMonths(3)}}
Sofia Grunspan
Contributor
June 20, 2023

I've used it but didn't work SV.JPGSVR.JPG

Mark Segall
Community Champion
June 20, 2023

Can you please share a screenshot of your rule's audit log?

Sofia Grunspan
Contributor
June 20, 2023

It appears like success but the value is empty or not shownal.JPG

Mark Segall
Community Champion
June 21, 2023

Hmm... I've tested in my environment and it works.  Can you please share a screenshot of the full rule?  The log shows that a branch is involved.  It would help to see the full context of what you're trying to accomplish.

Sofia Grunspan
Contributor
June 21, 2023

This rule is aimed to creates a task the first working day every 3 months with summary, description and due date and transion it to In Progress status. rule.JPG

Mark Segall
Community Champion
June 21, 2023

Ahh - Thanks for the added context.  I understand the issue now.  With the trigger being a schedule, there is no "Created" yet.  That's only going to happen AFTER the create issue action hence the blank due date.  Based upon this, you want to use this smart value instead:

{{now.plusMonths(3)}}
Sofia Grunspan
Contributor
June 21, 2023

Now it worked. Thank you so much!  

Like Mark Segall likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events