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

Automation on creating Epic (under issue) in advance X number of week from current date

Kaniawati Zainal Abidin

Hi all,

Good evening to all. I am new with jira. Appreciate our community guidance as I need to make an automation to create a Epic for each future Sprint for X number of weeks ahead (eg. 4 weeks ahead).

The Epic naming convention is "Sprint Week X" where X is the week number of the current year (eg currently today is 27 March so we are in Sprint Week 13.

Each sprint Epic is a duration of 2 weeks

eg.

- for year 2024, Starting 1 Jan 2024 (coincidently is a Monday) and end 14 Jan 2024 which is a Sunday as the 1st Epic which we named Sprint Week 1

- 15 Jan 2024 (Monday) till 28 Jan 2024(Sunday) as our 2nd Sprint in year 2024 which we named Sprint Week 3

- whereby currently it is 27 March, so we are in Sprint Week 13 which started from 25 March (Monday) 2024 till 7 April 2024(Sunday)

So this automation i plan to run under the automation trigger "When:Scheduled" for every two weeks on a Monday and will create a new Sprint Epic 4 weeks ahead (eg. on 8 April morning, the automation will execute and create a new Sprint Week tittle of 4 weeks ahead with tittle "Sprint Week 19" which starts from 6 May till 19 May 2024).

This is what i had configured but not able to get the naming convention right (as i could get the current week of the year but not get the future week number). @Guy Anela i think the rule was not running even when i did the "run rule" force manually is either due to the JQL search (which i had removed asper screen short mock test VS the original i did as per screenshot schedule). But i did also specify the project as per your advice (did not use the original "same project").

Also to set the Epic start and End date, is there a more suitable/efficient Jira Smart Value feature than "{{now.plusDays(x)}}" as the 2 weeks i may not always "start on a Monday/end on following Sunday" during end of the month as the different number of days in a month.

Appreciate advice.

Thanks @Guy Anela @Jack Brickey on the other thread. just knew how to create new thread for this specific query. Thanks creatre_epics schedule.jpg creatre_epics schedule (mock test).jpg creatre_epics overview.jpg creatre_epics PlusWeek.jpg creatre_epics Week4.jpg creatre_epics WeekYear.jpg creatre_epics View result.jpg

Accepted answers

Trudy P Claspill

Hello @Kaniawati Zainal Abidin

Your first problem is that you have misunderstood what the functions do.

plusWeeks() returns a date/time, not the week number for the date you provided.

weekOfYear is not a valid function at all.

You can find the documentation for available functions related to date/time data here:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/

If you want to get the week number for the current date, you need an entirely different function.

If you look near the top of the page I referenced you'll find a table talking about built in formatting functions for date/time. The last entry in that table refers you to another document with the codes to allow you to create custom date/time formats.

https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html

From that document you will find that using the code "w" will give you the week of year for a date/time you supply:

If you want to modify that number and still have it be just a number, say add 2 weeks to it so that if the current week of year is 13 then the final number is 15, you would additionally convert the value to a number and then apply the "plus()" math function.

That is the type of smart value you should be using in the Summary field where you want to specify "Sprint Week #".

I'm still considering the other questions you raised in your post. I'll get back to you.

Guy Anela_onntyg

Hi @Kaniawati Zainal Abidin - On your Create Issue Action, try something like this...

All comments

Kaniawati Zainal Abidin

sorry, seems the screenshot was not attached when i thought i had inserted earlier (which i had not as did not press the button) for reference. Here it is. sorry for the inconvenience

Trudy P Claspill

Hello @Kaniawati Zainal Abidin

Your first problem is that you have misunderstood what the functions do.

plusWeeks() returns a date/time, not the week number for the date you provided.

weekOfYear is not a valid function at all.

You can find the documentation for available functions related to date/time data here:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/

If you want to get the week number for the current date, you need an entirely different function.

https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html

From that document you will find that using the code "w" will give you the week of year for a date/time you supply:

That is the type of smart value you should be using in the Summary field where you want to specify "Sprint Week #".

I'm still considering the other questions you raised in your post. I'll get back to you.

Kaniawati Zainal Abidin

Thank you very much @Trudy P Claspill this "conversion" really helped with the Sprint naming and this give me hope that we can do automation with out the "rest API" which i'm trying very hard to able to understand using it . Very much appreciated on your simplicity solution.

I did not know that we could do the similar syntax (i only knew this is in SQL using "as" to represent something) ".asNumber.plus(x)" and make the resutl into number value for math calculations. This worked so well for the Sprint/Epic tittle naming for 4 weeks ahead. TQVM

creatre_epics WeekAdd4.jpg

And now to make this automation work fully, i will need to use the automation scheduler as below that runs every two week, and the above automation will create a new epic/sprint that is 4 weeks ahead

creatre_epics runEvery2Week.jpg

The only gap i'm trying to find solution is on how to make sure the sprint/epic start day is always the Monday of the mention week and the due date is always the following week of the Sunday (whereby each sprint/epic is a 2 weeks duration)

creatre_epics date.jpg

As in today example 1st April, i'm able to just add 28 days using

so the sprint Week 18 starts on 29 April and add another 41 days using

so the sprint ends on 12 May 2024, but this only works for the month having 30 days.

creatre_epics WeekAdd4result.jpg

Any suggestion on how to make this automation work no matter how many days in the calendar month? I can only think of the logic having:

- start date as 4 weeks ahead with the Monday as the date, and

- due date as 5 weeks ahead with the Sunday as the date

But not sure how to configure/use what function in Jira automation. Saw the function "OfTheMonth" but saw the sample return of the day and not the date. Was not able to find (just guessing if there was) function "OfTheWeek".

Thanks in advance.

Guy Anela_onntyg

Hi @Kaniawati Zainal Abidin - On your Create Issue Action, try something like this...

Trudy P Claspill

Hello @Kaniawati Zainal Abidin

To be clear, what you are doing with this automation is creating an issue. This automation is not actually creating a sprint.

And when you say you want to set the start and due dates, you are setting those for an issue, which is not the same as setting the Start and End dates of a sprint.

So, I'd like to confirm that it is your intention to be using the automation to create an issue, and not a sprint.

Guy Anela_onntyg

Hey @Trudy P Claspill - I'll let @Kaniawati Zainal Abidin respond but wanted to give you some context. This stems from this original Community post...

https://community.atlassian.com/t5/Jira-Software-questions/Re-Re-set-up-automation-creating-new-sprint/qaq-p/2651810/comment-id/934757#M934757

Based on that, I believe Kaniawati does eventually want to create Sprints with the Automation but is simply testing with Epics just to get the Naming convention and Start/End Dates correct before diving into the API calls needed to make the Sprint. ...that's my guess. Again, I'll let Kaniawati confirm.

Cheers!

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