Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Is there a way to get notifications on errors/misconfiguration in jira service desk

Patrik Björkman November 1, 2022

We recently got a popup "This service project has configuration problems and may not work as expected." due to a email account issue. This was only visible when opening the project.

Is there a way to get an email or slack notification when things like this occur ?


Thanks

//P

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 1, 2022

I am afraid there is not.

The problem is that Jira does not check the configuration of every project every time an email account is changed, and it only does some checks when the admins are configuring the project.  There's no event fired that could lead to an email or slack notification.

Patrik Björkman November 2, 2022




Connectivity log

Jira Service Management attempts to connect to (and pull new messages from) your custom mailbox every 60 seconds. The connectivity log shows the history of the result of each attempt. The top row shows the current status.

To make unsuccessful connections easier to find, we only show one line for each change in status, regardless of how many times the connection was checked.

To see how long a specific status persisted, check the times and dates under the To and From columns.

Each line shows how long each status lasted for, and any details about unsuccessful connections. The columns show:

Status – Whether the connection was successful or unsuccessful.

From – When the successful or unsuccessful connection began.

To – When the status was last checked before it changed to another status.

Details – Details about what happened if the connection was unsuccessful.

Statuses include:

Success – Jira Service Management successfully connected to your mailbox.

Failed – Jira Service Management couldn’t connect to your mailbox.

Rate limited – There were five failures in a row. To avoid overloading your system, Jira Service Management began increasing the time between each check – up to a maximum of one check every 24 hours – until a successful connection was made.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events