Automation: Urgent issue alert: how can you change the project default?

[Steven Bortels]

Dear,

When navigating to the according project > Project Settings > Automation, we have a list of alerts.This issue regards the 'Urgent issue alert'.

The person who automatically sends out this alert (i.e. the project default) used to be the project lead of the according project, lets call her S. This meant that S was the project default of the 'Urgent issue alert'. Yet the project lead is now A an no longer S.

The requirement is that A is the person whose name is mentioned when the 'Urgent Issue alert' is sent out.

We have tried the following: Deleting the existing 'Urgent issue alert' and created a new one, when the project lead was already A and no longer S. When checking who was the project default, it was still S. 

How can we change this?

Please see below a screenshot of the 'Urgent Issue alert':

If you wish for more information, please let me know.

Thank you in advance for your help! 

[Manoraj Kenchugonde]

Hi Steven Bortels,

Is this JSD Server or Cloud? Please tag it to jira-service-desk-cloud/jira-service-desk-server to get the response faster.

Also, are you using any add-on plugins?

Regards,

Manoraj K

[Steven Bortels]

Hi @Manoraj Kenchugonde,

I'll believe this is Cloud yet I'm not sure. 

I'm not using add-on plugins. 

Kind regards,

Steven

[Manoraj Kenchugonde]

I have tagged this question in 'jira-service-desk-cloud'. Let's see if someone reply to this.

[Steven Bortels]

Hi @Manoraj Kenchugonde ,

Thank you!

Kind regards,

Steven

[Steven Bortels]

Dear,

I've also tried the following:

Recreating the 'Urgent issue alert' and making sure that A is not in the list of people to which the alert is sent out.

This did not work either as S was still mentioned as 'Project default'. 

More information regarding the question: 

In the 'Summary' of the according project, you can see the following:

It is S who's name is mentioned under 'Components'. It is S who set up Jira for this project. Could this be the reason why S is still mentioned as 'Project default'?

Could you please look into this?

Thank you very much in advance!

Kind regards,

Steven

[Steven Bortels]

Dear Atlassian Community,

Could you please provide me with feedback on my question?

Thank you in advance! 

Kind regards,

Steven

[Steven Bortels]

Dear @Manoraj Kenchugonde ,

Could you please give me feedback on my question?

Normally I receive an answer very quickly from the Atlassian Community.

Is it because there there are already comments on this "ticket"? 

Thank you in advance!

Kind regards,

Steven 

[Manoraj Kenchugonde]

Hi @Steven Bortels

I'm really sorry about the delayed response. I was looking at the JSD server issues and wasn't sure that this issue is in Cloud or Server version. Hence, asked for more clarifications to tag it properly. Since this issue is in the cloud, I tried to figure out someone who can help in this regard and couldn't find anyone.

Comments on this ticket might be one of the reasons as well that you didn't get any response yet. 

[Vasilia Koulouri]

Hi @Manoraj Kenchugonde 

Could you please provide an update on the above?

Thank you in advance for your kind support!

Kind regards,

Vasilia

[Rashi]

Hey Steven, 

I am from JIra service desk cloud team, we tested this out and confirmed this is a bug. We have created a bug and here is the link:  https://jira.atlassian.com/browse/JSDCLOUD-8218

We will post further details on the bug, feel free to watch and comment it.

Warm regards,

Rashi

[Vasilia Koulouri]

Dear,

In ticket https://jira.atlassian.com/browse/JSDCLOUD-8218 you would fix this bug.

But the ticket was closed as not being a bug, if this is not a bug how can we fix this problem instead?

Thank you in advance.

Kind regards,

Vasilia