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

Custom Email for Issue update

Currently we have EPIC, User Story and Bug which we would like to receive notification email.

for different activity, the title and content of email varies (we wish).

1. When user update assignee - Email [JIRA] Assignee updated to xxx

2. When status transited - Email [JIRA] Status updated from Open to Close

3. When new comment added by jira user - Email [JIRA] Comment added by xxx [Content not shown - click link for details]

4. When new comment added by git user (special case when there is codes committed from Git and trigger automated comment updated with Git link) - Email [JIRA] New codes merged

for such use cases, should we use the email template?

or Automation Rule could helps better?

Accepted answers

All comments

Sebastian Krzewiński

Hi @JG

I'm guessing that you are not writing about JSM. IMO:

- for notifications 1 and 2 you should use notification scheme

- for notifications 3 and 4 you can use automation rule

Regards,

Seba

could you give me samples about the trigger, condition and content for #3 and #4?

for #1 and #2, which event should I remove them after create automation rule?

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center