Due Date Manipulation of Cloned Issue

I have a rule that clones an issue.  One of the fields being copied is called ‘Frequency’ and holds values of Weekly, Monthly, Quarterly, Semi-Annually, Annually.  When the new issue is created, I need to ‘apply’ this Frequency value to the due date of the original issue do determine how far out to make the Due Date of the new issue. 

So, if the original issue had a Frequency of ‘Quarterly’ and a Due Date of July 1, 2017, the cloned issue would have a Due Date of October 1, 2017.  Any help you can offer as to how to accomplish this in the rule for the frequencies listed would be greatly appreciated.  Thank you!

1 answer

1 accepted

0 votes
Accepted answer
Andreas Knecht Community Champion Oct 23, 2017

Hi Bill,

So we don't support this very well yet (what you really want is some way to create a mapping of values - https://codebarrel.atlassian.net/browse/AUT-173).

For now you'd have to create another rule like this:

  • Trigger: Issue created
  • JQL Condition: To match the newly cloned issue
  • Branch/Related issues action with 'Current issue'
    • JQL condition: Frequency = Weekly
    • Edit issue action and set due date: {{#issue.duedate}}func=plusWeeks(1){{/}}
  • Branch/Related issues action with 'Current issue'
    • JQL condition: Frequency = Monthly
    • Edit issue action and set due date: {{#issue.duedate}}func=plusMonths(1){{/}}
  • ...

See https://codebarrel.atlassian.net/wiki/spaces/AUTO4J/pages/24903696/Working+with+Dates for more details on available date functions.

So the idea is that you have another rule that listens for when the issue gets cloned (ensure this rule can be triggered by another rule in 'Rule details') and then for each of the different values of the 'Frequency' field it edits the issue with the appropriate future due date.

Hope this helps. Like I said it's a bit cumbersome, but we don't have a better solution at the moment.


Andreas, thank you for the suggestion and your time.  I will give this a try!  -Bill

Andreas, I have your suggestion basically working but have one question.  In the second step of your new rule you say to add a JQL Condition to match the newly cloned issue.  I can not find how to do this.  Can you help?  Thank you, Bill

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Marketplace Apps

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,691 views 3 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you