Hello everyone, everything good? lease, I believe that this doubt is basic for many, but ultimately I was not able to reach the result I expected. I have a project and within them there are hundreds of Components, I would like to make an automation that does the following: * Trigger when creating a subtask. * Make a public comment. * Assign those responsible * After all change the status to Done. My problem is that when creating this automation it is functional in all my project, that is, whenever someone creates a subtask (in any component) the automation works. I just wanted it to work in a single component, so it doesn't hurt other teams. I don't know if I managed to explain it well, but the attached print, and the automation I created.

I will test it and post the result here. Tim thank you very much for your patience and cooperation. Here in Brazil it's already 18:20 pm on Friday, the body has to rest a little. rsrs As soon as I test it I'll let you know.

You could use the issue updated trigger and add the condition for component back. That should work I think.

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

Questions to create a JIra automation

Rodrigo Xavier_5dax6g

Hello everyone, everything good?

lease, I believe that this doubt is basic for many, but ultimately I was not able to reach the result I expected.
I have a project and within them there are hundreds of Components, I would like to make an automation that does the following:

Trigger when creating a subtask.
Make a public comment.
Assign those responsible
After all change the status to Done.

My problem is that when creating this automation it is functional in all my project, that is, whenever someone creates a subtask (in any component) the automation works.
I just wanted it to work in a single component, so it doesn't hurt other teams.
I don't know if I managed to explain it well, but the attached print, and the automation I created.

Accepted answers

All comments

Hana Kučerová

Hi @Rodrigo Xavier ,

welcome to the Atlassian community!

I believe what you need is to set the scope of the rule to the single project.

It can be found in the Rule details section.

Rodrigo Xavier_5dax6g

Hi @Hana Kučerová

Thanks a lot for the quick feedback.
I had looked before but I didn't find any relationship.
Would I have to change the "Actor" field?

Tim Perrault_xzdboh

Hi @Rodrigo Xavier

I think I understand what you want. I would try something like I have in my screenshot:

Hana Kučerová

Thank you.

I can see the scope is ok - single project LPBR ICT.

I didn't understand you correctly.

Probably @Tim Perrault is right, you need to add condition with your component.

Rodrigo Xavier_5dax6g

Hi, @Tim Perrault sorry I didn't see your message.
Thanks a lot for his answer.
I don't know if it could be the configuration that my organization made but I don't see some components and fields, as I see in my test environment.
I tried to use this same rule, but I didn't find the Issue Type for example.
Would it be possible to do this with JQL?

Tim Perrault_xzdboh

Both the conditions I used were the Issue fields condition. Are you not able to select Issue Type in the Field section?

But yes using the JQL condition should also work.

issuetype = Sub-task

Rodrigo Xavier_5dax6g

I managed to find the field, I was looking in the wrong place sorry. I did the same test as your print and then I reversed the component, in both cases it shows the message.

ACTION DETAILS:
ISSUE CONDITION
The following issues passed:
LPBRI-663

ISSUE CONDITION:
The following issues did not match the condition:
LPBRI-663

Rodrigo Xavier_5dax6g

Hello @Tim Perrault @Hana Kučerová everyone, everything good?
Tim managed to do the automation here.
I left it that way and even acted ps other teams didn't complain about subtasks being automatically closed, so I believe I managed to reach the desired result. Now just refine the code.
Thank you very much for your partnership and help. Automation was like that.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-cloud

automation

new-to-jira