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

Automating Issue Creation

Matt Hine

Hi,

I'm looking to automate creating a new issue on project 2, when project 1 is transitioned to a given status. I appear to have done this part as it works as I want it to. However, part of the automation is to send an email to advise project 2 that the task has been created and this isnt working as i'd hoped.

Having reviewed other posts on here, I found the user of the "trigger" smart value but believe this will reference project 1 when i want it to quote the issue key and summary for project 2. . Can anyone advise what i need to use?

Also in future, I would like to look at replacing the email with a comment in jira instead where I would tag the team/users? I assume I would use the "comment on issue" instead and in the comment tag the user(s). Again, how would i ensure that this was added to project 2?

Automation rule.PNG

Thanks in advance

Accepted answers

Alex Koxaras -Relational-

Hi @Matt Hine

Can you provide the rule you created so far?

All comments

Alex Koxaras -Relational-

Hi @Matt Hine

Can you provide the rule you created so far?

Matt Hine

@Alex Koxaras -Relational- Apologies, i have now included this. I have removed the email content as it was my work email and didnt quote the subject that i wanted it too.

Please can you also confirm that the "link to issue" will show that the project 2 issue is blocking project 1?

Thanks

Alex Koxaras -Relational-

@Matt Hine thank you for sharing the rule!

Question, why you want to send an email? I mean project 2 will already have a notification scheme, which you can configure and this scheme will send all notifications to the respective people you choose in it. Yes, the link component can link an issue to another.

Keep in mind that you have to have the create issue permission to project 2.

Matt Hine

@Alex Koxaras -Relational- Its part of the current process that we notify the team (project 2) of the issue. Project 2 is currently using the default permissions scheme (used by the majority of projects), so only watchers, reporters and assignees get notified when a issue is created.

We have permissions for project 2, but we're not the admins so are trying not to change too much of what they do. The main aim is to automate the task we create for this team inline with the current process. When time allows, we'll look to review this with them as there are a number of factors impacting this.

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk-cloud

automation

smart-value

jira-service-management-cloud