In the Timeline of a Plan is it possible for epic start and end dates to automatically move when the previous epic's end date is changed? For example, in the screenshot below, the end date for epic TM-252 is 'Mon, Jul 15, 2024'. This epic blocks the next epic TM-267, which currently has a start date of 'Tue, Jul 16, 2024'. If I extend the end date of TM-252 to 'Mon, Jul 15, 2024', the dependency link changes to red to show that the two epics are now running concurrently (overlapping by 12 days) and not consecutively: Is there a way to automate epic TM-267's start AND end date to move on 12 days so that the two epics are running consecutively again and no longer overlap?

Hi @Maxine Freedman-Thompson , I'm curious... how fares your automation effort? I landed here while looking for a similar solution.

Hello @Maxine Freedman-Thompson No, not exasperated at all! I've just been really busy with work on Cloud migrations. An excellent tool to use in debugging rules is the Log action. https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Log-action With that action you can write text and values into your rule execution Audit Log. Did you notice the Audit Log link in the upper right corner? If you click that you go to a screen that shows you a log for each time you saved changes to the rule and each time it executes. If you click the Show More link to the right of one of the entries, you get more detail for that entry. I recommend using Log actions to write the following values into the audit log to confirm the rule is getting the values you expect. First, the before and after values of the changed field: * original value: {{fieldChange.fromString.toDate}} * new value: {{fieldChange.toString.toDate}} Then the calculation you did to get the difference between the two dates,: * days difference calculation: {{fieldChange.fromString.toDate.diff(fieldChange.toString.toDate).days}} Within the loop, write out the original value of each field you plan to change before you change it. Then write out the value you expect it to change to - that long smart value, i.e. * {{issue.End Date.plusDays(fieldChange.fromString.toDate.diff(fieldChange.toString.toDate).days)}} ...where End Date is the correct field name for your scenario (due date and start date?). You might want to be trying all this in a test project with a small data set of Epics, to get the kinks worked out before applying it to your production data. Share the output from the audit log with us. Let us know if the values appear to be correct. If they don't appear to be correct, tell us what you think the correct values should be. Are the destination Epic fields getting updated at all? Are they getting updated with the wrong values?

@Trudy P Claspill have I exasperated you!? Do you have any ideas as to why it's still not working for me?

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

In a Plan, can you automate an epic's start date to adjust if the previous epic's end date is extend

Maxine Freedman-Thompson

In the Timeline of a Plan is it possible for epic start and end dates to automatically move when the previous epic's end date is changed?

For example, in the screenshot below, the end date for epic TM-252 is 'Mon, Jul 15, 2024'. This epic blocks the next epic TM-267, which currently has a start date of 'Tue, Jul 16, 2024'.

Timeline 1.JPG

If I extend the end date of TM-252 to 'Mon, Jul 15, 2024', the dependency link changes to red to show that the two epics are now running concurrently (overlapping by 12 days) and not consecutively:

Timeline 2.JPG

Is there a way to automate epic TM-267's start AND end date to move on 12 days so that the two epics are running consecutively again and no longer overlap?

Accepted answers

All comments

Trudy P Claspill

Hello @Maxine Freedman-Thompson

You would need to set up an Automation Rule to do that. Are you familiar with Automation Rules?

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

Maxine Freedman-Thompson

Many thanks @Trudy P Claspill I'll take a look

Maxine Freedman-Thompson

Hey @Trudy P Claspill

Thanks to your suggestion I've summarised that I need to add automation rules for the start date and due date fields on my epics. However, I've discovered that when I extend or shorten the bar neither of these fields is updated in the issue screen, hence any automation won't work.

Do you know what I'm doing wrong or how I ensure that when the start date and/or due date is changed, either by dragging the bar on the timeline or by updating the fields on the issue screen the other is automatically changed? Looking at other threads, it looks as though this usually happens for other people.

Hold that thought, I think I've solved it

Trudy P Claspill

After dragging the bar to change the dates are you reviewing those changes and committing them to the underlying issues? The underlying issues won't be updated until you review and save the changes.

Screenshot 2024-04-25 at 10.56.20 AM.png

Screenshot 2024-04-25 at 10.56.39 AM.png

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

automation