Hi guys, I have a silly problem and I hope someone can help me :P When a general Jira ticket is opened under the IT board, I am the only one who receives them. If I am on leave, for example, the team won't see anything without exploring the board for new tickets. We have had some problems because of this. I would like to change this to a group email so the whole IT team will receive notifications about a new ticket. Under the Project Settings I found: * Project lead: Myself * Default Assignee: Project Lead. If my logic is right, I would need to: * create a user which uses a group e-mail as e-mail * unfortunately, consume a license for that * come back here is change the project lead * the whole team will be notified Am I right??? Is there any other way??? No less important, some of the tickets from other projects are opened as Unsigned, under the "Default Assignee" there is an Unnasigned option so I believe I just need to change that. Thank you

Hi @Whisley Santos I would change Default Assignee to "Unassigned" instead. Default Assignee can only be Unassigned or Project Lead. There are better methods for notifying the team than created a central account - such as: * Subscription: You can set a subscription up after saving a filter via the "Details" hyperlink (next to the filter name). This sends an email each scheduled timeframe to a group of users. So you could filter for new issues and have it send the list to your team every 15 minutes (or similar). * Automation: Manage notifications via automation - for example when a new issue is created it could send an email to your team, or one nominated user. Or it could create a comment on each ticket and @mention them. * Components: You can override Default Lead by setting the assignee to be the "Component Lead" per component. The benefit of Component Lead is you could set a different assignee depending on the component applied to each issue! * Board: Have a board where all new issues go that can be viewed by the team * Dashboard: Similarly, have a dashboard with a filter gadget for new tickets - ordered by created date (newest > oldest) Lots of options! Let us know if any suit your needs - or if you need any more specific instructions to implement one of these :) Ste

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

How to change the user receiving the jira ticket e-mails?

Whisley Santos_ihi4k8

Hi guys,

I have a silly problem and I hope someone can help me :P

When a general Jira ticket is opened under the IT board, I am the only one who receives them. If I am on leave, for example, the team won't see anything without exploring the board for new tickets. We have had some problems because of this.

I would like to change this to a group email so the whole IT team will receive notifications about a new ticket.
Under the Project Settings I found:

Project lead: Myself
Default Assignee: Project Lead.

If my logic is right, I would need to:

create a user which uses a group e-mail as e-mail
unfortunately, consume a license for that
come back here is change the project lead
the whole team will be notified

Am I right??? Is there any other way???

No less important, some of the tickets from other projects are opened as Unsigned, under the "Default Assignee" there is an Unnasigned option so I believe I just need to change that.

Thank you

Accepted answers

Ste Wright

Hi @Whisley Santos

I would change Default Assignee to "Unassigned" instead.

Default Assignee can only be Unassigned or Project Lead.

There are better methods for notifying the team than created a central account - such as:

Subscription: You can set a subscription up after saving a filter via the "Details" hyperlink (next to the filter name). This sends an email each scheduled timeframe to a group of users. So you could filter for new issues and have it send the list to your team every 15 minutes (or similar).
Automation: Manage notifications via automation - for example when a new issue is created it could send an email to your team, or one nominated user. Or it could create a comment on each ticket and @mention them.
Components: You can override Default Lead by setting the assignee to be the "Component Lead" per component. The benefit of Component Lead is you could set a different assignee depending on the component applied to each issue!
Board: Have a board where all new issues go that can be viewed by the team
Dashboard: Similarly, have a dashboard with a filter gadget for new tickets - ordered by created date (newest > oldest)

Lots of options! Let us know if any suit your needs - or if you need any more specific instructions to implement one of these

Ste

All comments

Ste Wright

Hi @Whisley Santos

I would change Default Assignee to "Unassigned" instead.

Default Assignee can only be Unassigned or Project Lead.

There are better methods for notifying the team than created a central account - such as:

Subscription: You can set a subscription up after saving a filter via the "Details" hyperlink (next to the filter name). This sends an email each scheduled timeframe to a group of users. So you could filter for new issues and have it send the list to your team every 15 minutes (or similar).
Automation: Manage notifications via automation - for example when a new issue is created it could send an email to your team, or one nominated user. Or it could create a comment on each ticket and @mention them.
Components: You can override Default Lead by setting the assignee to be the "Component Lead" per component. The benefit of Component Lead is you could set a different assignee depending on the component applied to each issue!
Board: Have a board where all new issues go that can be viewed by the team
Dashboard: Similarly, have a dashboard with a filter gadget for new tickets - ordered by created date (newest > oldest)

Lots of options! Let us know if any suit your needs - or if you need any more specific instructions to implement one of these

Ste

Whisley Santos_ihi4k8

Hi @Ste Wright ,

Thank you for your reply.

Leaving the default as "Unassigned" will create more problems than solve them. This is actually one of the problems, nobody seems/notice the unassigned ones. Tickets like a month old because nobody noticed them, no e-mails sent.

All we need is a way to make the whole team to receive the notification, once, that is all. So you can check the e-mails and start from there.
We already have dozens of notifications with timeframe --- ICT Infrastructure & DevOps Engineer world I guess --- so I am avoiding adding one more to the chaos.

"Automation" seems to be more what I am looking for. I will try to find more documentation about it. If you have any please, feel free to share.
I am closing this

Thank you for your help.

Ste Wright

Hi @Whisley Santos

There's some great information for Automation in the Knowledge Base - see this central resource as a good place to start.

Automation is either at project or global level - to access it:

Project: You'll need to be a Project Admin - go to: Project Settings > Automation
Global: You'll need to be a Jira Admin - go to: Jira Settings > System > Automation Rules

I would advise utilising "Project" for a rule like this. This is because global executions per month are limited - for Cloud Standard, this is 500 executions, per Atlassian product, per month.

For Project - executions are virtually unlimited.

If you need any assistance building out a specific rule - let us know and I'd be happy to help

Ste

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software