How to automate duedate update according to blocked issues

[Asaf Anter]

I have issue A with some duedate 

I want to cerate issue B and mark it as "blocked by" issue A.

I also set estimate time of 2d for example.

I want on the creation that duedate of B will be as the duedate of A + estimate of B

So if the duedate of A is 20.6.23 and estimate of B is 2d, so after creation of B the duedtae of B will be 22.6.23

[Walter Buggenhout]

Hi @Asaf Anter and welcome to the Community!

That sounds like an interesting use case. It seems as if you are trying to automate the schedule of a roadmap of some sort.

While I am having some doubts about your actual use case, you should be able to create and link a new issue using an automation like this:

When you add an additional edit issue action, you can additionally update the issue's due date using a smart value like this:

{{triggerIssue.duedate.plusDays(2)}}

My doubts are about the scalability of your solution. Automation works best if you can repeat the process multiple times so it avoids manual work. I'm not sure if that is the case here. Also, keep in mind that you will probably also need automations for when the due date of an issue changes, ...

Hope this helps!

[Asaf Anter]

Why doubts?

I want to enter now 6 issues by order and set estimate time for each of them,

than I want to able and check the duedate of issue number 5

I think its a trivial need, I doing it with Excel and it so simple but the Excel itself not scalable

If you have another methodology to mange it I will be glad to here

[Walter Buggenhout]

My doubts are linked to the idea of automating the creation of a blocked issue (responding to the issue created event means you either have to build in a lot of conditions to avoid ending up with lots and lots of blocked issues you may not even need). I would consider rather using e.g. the issue linked trigger instead.

Also, when you start automating your due dates when you create an issue, I can imagine you will also want to make sure that your due dates are updated when something changes. That may happen when the due date of one issue changes, when you link an issue to another one, when an issue's due date passes and it is not complete yet. And so on ...

That is a lot of work to set up while you can update due dates with a simple drag and drop in the roadmap view of your project (or advanced roadmaps on a premium plan).

I have no ambitions to stop you from doing this - that's why I shared the automation rules and smart values to get you going. Just challenging you a bit on the underlying idea.