-
Bug
-
Resolution: Unresolved
-
Medium
-
33
-
Minor
-
7
-
Issue Summary
Agents don't get some internal notification when the agent is in JSM organization and the internal notification is configured to send notification to project role like "Service Desk Team".
This is partially fixed at https://jira.atlassian.com/browse/JSDCLOUD-3410, but still there is a case that agents don't get internal notification. It's been fixed to treat watchers and assignee as agents in JSDCLOUD-3410. However when an issue is created, it’s not possible to send internal notification to agents as there is no watcher and assignee at the time.
Steps to Reproduce
- add a user to a project as "Service Desk Team" role
- add the agent to a JSM organization
- configure the internal notification to send notification to Agent role users.
Expected Results
The user get the internal notification.
Actual Results
The user doesn't get the internal notification.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- derived from
-
JSDCLOUD-3410 I would like my Service Desk agent to receive JIRA notification even if they are a request participant/reporter/part of Organization
- Closed
- mentioned in
-
Page No Confluence page found with the given URL.
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
JSDCLOUD-3410
->As a result of checking the behavior, we confirmed that internal notifications to agents included in the customer organization are effective only when they are "All Watchers" and "Current Assignee", and that this is an event that prevents notifications when you want to notify roles such as "Agent" of "Request created".
We believe that this is a fatal problem.
We would like to request that the specification be made simple so that notifications can be made if it is an internal notification target.