Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Start and finish date of an epic with the max date of the tasks related

Hello,

For a project I want to set the start and finish date of each epic considering the max date of the tasks related. 

I really appreciate ideas to set a rule.

 

Regards

1 answer

1 accepted

0 votes
Answer accepted

Hi @Angelica Hernandez 

Are you asking how to do this with Automation for Jira rules?  If so...

I can think of a simple way to do this which does not handle all possible scenarios, and a more complicated way: The simple way assumes Start Dates only get earlier for tasks, not later, and that Due Dates only get later, not earlier.

With the simple way, you use one automation rule.  In my example below, I assume you mean Due Date as I do not see a Finish Date field in my Jira instance.  If you have a Finish Date field in your Jira instance, please substitute that field name.

  • Trigger: field value change for either Start Date or Due Date by an Edit operation
  • Condition: issue type is not epic
  • Branch: on epic (parent)
    • Advanced Compare Condition: {{triggerIssue.Start Date}} is not empty
    • Advanced Compare Condition: {{triggerIssue.Start Date}} is less than {{issue.Start Date}} (the epic)
    • Action: edit Start Date to the {{triggerIssue.Start Date}}
  • Branch: on epic (parent)
    • Advanced Compare Condition: {{triggerIssue.duedate}} is not empty
    • Advanced Compare Condition: {{triggerIssue.duedate}} is greater than {{issue.duedate}} (the epic)
    • Action: edit DueDate to the {{triggerIssue.duedate}}

The more complicated way uses two rules and can handle the dates changing in either direction, earlier or later.  Please let me know if you want me to post that information.

Best regards,

Bill

@Bill Sheboy , thank you so much! is Exactly what I needed.

Thank you for your complete responde, very useful 

Like Bill Sheboy likes this

I am glad to hear that helped you.  Please consider marking this question as answered; that will help others in the community find solutions faster.  Thanks!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you