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

How to move a ticket forward in timeline when is blocked by other ticket

Sara Mendes

Hello, on the Jira Timeline, when we encounter tickets blocked by others and subsequently adjust the due dates of those blocker tickets, we should observe a corresponding adjustment in the start dates of the tickets being blocked, by the same number of days as the blocking ticket's duration.

In this example, the second ticket is being blocked by the first, and the second should start at the end of the next ticket.

Screenshot 2024-03-04 at 19.30.32.png

How can I do this?

Accepted answers

All comments

Trudy P Claspill

Hello @Sara Mendes

The basic Timeline feature in a Standard Jira subscription will not automatically adjust issue dates.

You could use Automation Rules to automatically adjust the dates. There are several posts in this community on that topic.

https://www.google.com/search?q=jira+cloud+automation+change+dependent+task+dates

Some of the possible challenges you may run into are:

1. There is a limit of 1700 rule executions per month on the Standard Jira subscription. You will need to consider how often a rule to adjust dates might be triggered in a month, and how many other rule executions are occurring in your instance.

2. The rule implementation is recursive. It is triggered by the changing of the date of the prerequisite task, and then looks for and adjust dates of dependent tasks. If the dependent task itself is the prerequisite to another task, changing the dates of the dependent task would trigger the rule to run again. The limit on that sort of recursive triggering of a rule is 10 triggers.

Sara Mendes

Hi, today I was trying to achieve this by using the automation, but I couldn't put it working.

This is what i did:

Screenshot 2024-03-06 at 18.00.33.png

But for some reason, the only thing that is happening is that the ticket that is blocked has the same due date as the ticket that is blocking the other.

Screenshot 2024-03-06 at 18.00.55.png

And what I was expecting was that the ticket blocked changed the Start date to the same date that is on the Due date of the ticket that is blocking, and maintaining the same number of days.

Is that possible with automation?

Trudy P Claspill

Hello @Sara Mendes

Jira won't natively change the dependent task's due date just because its start date changed. You have to add the steps in your Automation Rule.

You need a Create Variable step to calculate the original duration of the dependent task.

Screenshot 2024-03-06 at 12.44.07 PM.png

Then in your Edit Issue task you can use the Copy option to update the Start date or use a smart value like I've shown.

For the Due date you need to use a smart value to change it, calculating a new date that uses the Duration you got in the previous step.

The plusDays function will add a number of calendar days. If you don't want to include weekends then use plusBusinessDays instead.

Screenshot 2024-03-06 at 12.44.21 PM.png

Sara Mendes

Hi, thanks for the exemption and the examples; it helps to understand and configure the Start date of the ticket that was blocked by the other correctly.

But for some reason, with your instructions, the Due date is not correct, is presenting a big number of days, and its not being added to the ticket

Screenshot 2024-03-07 at 09.47.01.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