JQL Start date information

[Aaron Micallef]

Hey Guys,

I am just searching for a confirmation to understand the start date JQL I am doing an automation to send a reminder slack/email msg to a team based on 3 days before the start date.

This is was I was going for project = CTI AND issuetype = "Casino - Lobby Update" and "Start Date[Date]" = startOfDay(3)

This here from the testing I did i think it does the job, what if i would like it to run from 3 days before until the start date? this is where I am struggling.

Cheers Aaron

[Ben Finn · Accepted solution]

Hi @Aaron Micallef

It may be a typo in your request but you need to set up start of day like this = startOfDay(-3d)

[Aaron Micallef]

Hello @Ben Finn 

when i do the  startOfDay(-3d) it will not show me nay issues when i do the advanced search but when i do "Start Date[Date]" = startOfDay(3) it does show as per below

[Ben Finn]

I just tested on my sandbox to confirm and can say that without the - it adds the days, so I would recommend you check the data and see if you have any issues with a startdate of November 21st (3 days before today). 

Alternatively I noted that the screenshot does not have a start date shown, are you looking for start date or another date?

[Aaron Micallef]

Correct since I want to receive a notification 3 days prior the start date I want it to add or I am getting it wrong? got a bit confused here.

[Ben Finn]

@Aaron Micallef  Haha. Hopefully I am not confusing you. Ill try to be straightforward (maybe it is what you understood but this will help us align).

If you run the following today in JQL you will get the following results

1.  "Start Date[Date]" = startOfDay(3) then this will find all Jira tasks with a start date of November 27th.

2.  "Start Date[Date]" = startOfDay(-3) then this will find all Jira tasks with a start date of November 21st.

Based on the screenshots above (where you ran project = CTI AND issuetype = "Casino - Lobby Update" and "Start Date[Date]" = startOfDay(-3)), you have no Casino Lobby Update issues in the CTI project where the start date is November 21st. 

I would recommend confirming this by looking at your data. If you can confirm that than we can take another look and see if there are any other issues but that is what I see right now.

[Aaron Micallef]

this here is exactly what i need :) 1.  "Start Date[Date]" = startOfDay(3) then this will find all Jira tasks with a start date of November 27th.

I want to be notified before that starting date which is in 3 days before, than if it would be possible to continue get notified until the start date not prior the 3 days not later than the 3 days

[Ben Finn]

I see your approach now. You want to inform them of upcoming work, not remind them of work they should have started. I had a client who wanted the later so apologies for adding to the confusion :).

 "what if i would like it to run from 3 days before until the start date?" With my understanding now, I assume you want to remind them every day starting 3 days before. i.e. an email/slack 3 days before, an email/slack 2 days before, an email/slack 1 day before and an email the day of. Is that correct?

If I understood you correctly, a daily automation with a JQL if statement of the following should do it.

"Start date[Date]" <= startOfDay(3) and "Start date[Date]" >= now()

Is that what you are looking for?

[Aaron Micallef]

Yep this is exactly what i need, I can see it is working with you suggestion, apologies for the confusion.

I will apply this, thanks a million :) 

[Zola Schmidt]

Automating notifications is a fairly reliable approach to keeping everyone up to date. By the way, many IT companies would like to implement a similar approach. I know that the guys from https://kaszinoworld.com/20bet/ tried to create something, but I'll have to ask if it worked out. In my opinion, instead of focusing on just one day, you could use something like startOfDay(-3)and , endOfDay() to cover the range.

[Keni Yadrami]

Your idea makes sense and can be useful, but it's important to consider that automation requires careful configuration to avoid excessive notifications and ensure their value for the end user. Also, one should not forget about the context and the flexibility of the approach depending on the situation.