Check date when Transition occured

[SputnikCZ]

Hi gurus! 

I'm getting used to asked stupid questions here. Please stop me if it is stupid now :D

So, I'm currently trying to set few automations for ticket transitions for cross-projects.

1st automation is for:
Send "email" to "asignee" IF status = "Check" AND date of transitions =>14, send only once

I struggle with the smart-values and JQL to find a proper checker for "when transitioned FROM 1 TO 2" where the WHEN represents DATE checker.

2nd automation:
Project A, Project B, Project C
Project A creates a ticket for Project B, Project B checks and if needed, creates a ticket for Project C.

I have currently 3 different automations for this and would like to put all into one but when I tried, I was receiving only errors (I still don't understand completely the JQL and smart-values)

Now I want to do the following:

Once ALL of linked issues from Project C in Project B ticket are "RESOLVED", Resolve automatically the project B ticket.
Once ALL of linked issues from Project B in Project A ticket are "DONE", Resolve automatically the Project A ticket.
Close the project A ticket also if all linked Project C tickets are "RESOLVED", WHEN:
Ticket A created >28d = Close as "DONE"
Ticket A created <=28d = Put into "Awaiting confirmation"

Project A is for a direct contact with reporters, so the date checker should be only here from the whole automation.

The "Awaiting confirmation" is being set in different automation where it is also divided for 4 different statuses in Project A.

Not sure if it is possible to create one automation for all of the above (2nd automation) or if you would suggest to create a separate automations for this big whole nonsense.

[Jack Brickey]

Hi @SputnikCZ , if you are trying to send an email to the assignee if the issue has been in a certain state for more than 14 days, then consider the following approach...

trigger - scheduled daily

condition - JQL - Status = "Check" and status changed before -14d

Action - email

with that said, I'm getting a little bit lost with the rest of your automation.

[SputnikCZ]

Hi Jack.

Thanks! That JQL seems to be what I need :D 

What exactly got you lost in the second part? I will try my best to explain.

[Jack Brickey]

You mentioned that you are getting errors when you try to pull it all into a single automation. It would be good to understand what those errors are, as well as actually visualizing your automation. With this said, it is my opinion that you should not try to consolidate everything into a single automation rule when you have rather complex automations. My reasons are for formants, as well as considerations and maintaining the automations. However, not actually seeing your automations and fully understanding them limits my best recommendations.