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

Rules - add comment into the new ticket created

pclosas

Hi! I'm using a rule that creates a ticket into another board, copying the description, the attachments, addign a reporter, linking both tickets, etc

The rule is already adding the reporter the way I need into the new triggered ticket.

What I would like to do is within this rule, add a comment into the triggered (new created ticket) naming the reporter so they are aware of the creation of this new ticket in this other board.

Thanks!

Accepted answers

All comments

Sebastian Krzewiński

Hi @pclosas

In the same rule you can use branch item and set it to 'most recently created issue' and inside branch add comment action.

Screenshot 2025-02-12 at 08.55.29.png

Regards,

Seba

pclosas

Thanks Sebastian, I just tried an add it.. I'll test it with the next jira

Thanks a lot!

pclosas

Hi Sebastian, I tried but no comment is added in the new created ticket:

2025-02-17 12_18_17-Rule builder - Automation - Project Support - Jira.png

Bill Sheboy

Hi @pclosas

For a question like this, context is important for the community to help. Please post the following:

what type of project is this (e.g., company-managed, team-managed, etc.),
an image of your complete automation rule in a single image for continuity,
images of any relevant actions / conditions / branches,
an image of the audit log details showing the rule execution, and
explain what is not working as expected and why you believe that to be the case.

Until we see those...

Is your rule creating the new issue in a different Jira project than the trigger issue?

If so, what is the scope of the rule in the details at the top: single-project, multiple-project, or global?

While single-project scope rules can create (or clone) issues into other projects, they cannot access them in any other way. When you need to perform additional actions on the most-recently-created issue in another project, the rule must use a different scope.

To change the scope, your Jira Site Admin will need to do that in the site admin area for rules.

Kind regards,
Bill

pclosas

Hi Bill, thanks for answering

I add the answers here:

what type of project is this (e.g., company-managed, team-managed, etc.), I would say is team managed
an image of your complete automation rule in a single image for continuity,

2025-02-20 15_30_05-Rule builder - Automation - Project Support - Jira.png

images of any relevant actions / conditions / branches,

2025-02-20 15_49_41-Rule builder - Automation - Project Support - Jira.png

an image of the audit log details showing the rule execution (I'm lost here, I dont know where to find that)
explain what is not working as expected and why you believe that to be the case.

In the new ticket that is created thank to the above rule, I'd like to have an automation (within the existing rule) that adds a comment.

In this comment I'd like to name @ the reporter, which thanks to the automation before is the same as in the first jira (the original one, where the automations starts)

I tried doing the branch process, but I do not get the comment.

Example of the branch:

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