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

Create recurrent sub-task under a specific story

Alvaro Landin

Good afternoon,

I am trying to create a couple of recurrent sub-tasks that will be scheduled at the start of next month (on a monthly basis and on a quarterly basis depending on the task).

I am not being able to create the automation rule locating the sub-task under the desired story.

This is what I have by now. I don't find how to locate where I want the sub-task.

Kind regards,

Alvaro

Comments

Joseph Chung Yin

@Alvaro Landin -

Using automation rule is the way to handle your ask, however you will have to be able to identify which parent task that you need the recurring subtask(s) on a schedule based trigger.

It is important that you need to determine what are the criteria of your parent task that needs the subtasks. So, I would recommend that you take a step back to figure that out first. Once you have done so, then you can use automation rule to complete your process.

Without determining which parent task(s), then the rule is not going to helped you.

Hope this helps.

est, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Jack Brickey

Hi @Alvaro Landin , in your rule above could you share the details of the create action? Is the parent static (always the same? What error is presented in the audit log?

Alvaro Landin

Hi Jack,

Sure, please find it below.

Yes, indeed. It is a static parent (a story).

The error I found is the following:

Apart from that, I still cannot find how to locate the recurrent issue where I want.

Kind regards,

Alvaro

Alvaro Landin

Hi @Joseph Chung Yin

I do know which is the parent task I want to link to.

However, I do not know how to locate the recurrent task where I want. It is a static parent, if that helps.

Let me know!

Jack Brickey

Thanks for the screenshot. As I suspected, you're not correctly identifying the parent. It appears you are selecting "current issue" when the trigger is a scheduled event. You can only use current issue if it is defined within the context of the rule. Such as what triggered the rule. If, indeed, this is a static parent, then simply define the issue by the issue key where you have "current issue". Type the key and then select what is presented as issue abc-xxx.

example...

Joseph Chung Yin

@Alvaro Landin -

In addition to what @Jack Brickey suggested, you can also experiment with using local variable where you can specified your parent (static issuekey), then you can refer to the local variable in the Create Issue Action -

Hope this also helps.

Best, Joseph

Alvaro Landin

Hi @Jack Brickey again for the response,

However, I tried to include my parent issue code in the Parent Issue field and it was impossible to save it. Each time I type it a message saying "No options" appears.

Do you know why could be this happening?

Kind regards,

Alvaro

Alvaro Landin

HI @Joseph Chung Yin ,

Thanks for the alternative solution. However, I still find some errors while using this solution. I have defined it like in the picture below.

Additionally, with his solution, how the rule know which should be the parent issue?

Kind regards,

Alvaro

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira-software-cloud

jira-software-server

advanced-roadmaps

unknown-hosting-type