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!
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.
Regards,
Seba
Hi Bill, thanks for answering :)
I add the answers here:
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:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information.
To find the audit log and post the image...
In the comment, if you want to mention the reporter so they get notified, replace the email address information in the comment body with this:
[~accountId:{{createdIssue.reporter.accountId}}]
Also, please note my question about the rule scope. If your rule is single-project scope, it cannot add a comment to an issue created in a different project.
Instead the rule must be changed to at least multiple-project scope.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Bill!! I see what you mean and all make sense. Thanks a lot!
I checked the audit log:
and the scope:
I will contact my Jira Admin to see if I can get the scope issue solved.
Thanks a lot for your detailed answers :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @pclosas
For a question like this, context is important for the community to help. Please post the following:
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.