-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
6
-
User Problem
Currently whenever a request participant is added to a thread , we notify the added participant in the requester thread that exists in a channel.
But There are use-cases where the issue is raised outside of the slack channel. In this case , the request thread exists in a DM with the bot.
Any added participants to the jira ticket are not notified on slack in this scenario.
Additionally, if the request participant is not part of the request channel, they do not receive any notifications either.
Suggested Solutions
When the request thread exists in DM with the bot and any participants are added to the issue, send DM to the participant with the issue preview.
Also, notify the participant when any comment is added to the requester thread.
[JSDCLOUD-14414] Notify request participants for private threads
| Support reference count | New: 6 |
| UIS | New: 1 |
Wouldn't an easy solution be to message each person rather than @'ing them? Please add this feature as this is one of the limiting reasons why people wouldn't use this application over others.
| Description |
Original:
h3. User Problem
Currently whenever a request participant is added to a thread , we notify the added participant in the requester thread that exists in a channel. But There are use-cases where the issue is raised outside of the slack channel. In this case , the request thread exists in a DM with the bot. Any added participants to the jira ticket are not notified on slack in this scenario. h3. Suggested Solutions When the request thread exists in DM with the bot and any participants are added to the issue, send DM to the participant with the issue preview. Also, notify the participant when any comment is added to the requester thread. |
New:
h3. User Problem
Currently whenever a request participant is added to a thread , we notify the added participant in the requester thread that exists in a channel. But There are use-cases where the issue is raised outside of the slack channel. In this case , the request thread exists in a DM with the bot. Any added participants to the jira ticket are not notified on slack in this scenario. Additionally, if the request participant is not part of the request channel, they do not receive any notifications either. h3. Suggested Solutions When the request thread exists in DM with the bot and any participants are added to the issue, send DM to the participant with the issue preview. Also, notify the participant when any comment is added to the requester thread. |
Please bring this feature back ASAP. Without it, it is really affecting our flow when managing requests.
Agree with what others have said, please help prioritize this as users that were migrated from HALP to JSM already had this feature available. Thus there should be no blockers within Slack.
Any word on if we can bring back this functionality?
This is causing us to weigh up moving to a new ITSM that better integrates with Slack as a result.
We want request participants, and users to see all their tickets in Slack. The Slack Home tab for the app should be the only portal they need... we dont need to send these internal users to an external portal.
Managers or people added to a conversation, public or private, should be able to review the ticket in Slack.
What Tom said. Please bring it back!
We have plenty of situations where we want to bring someone else into the private ticket thread for Slack and now that ability is gone. We basically can't "cc" anyone now...
There are projects that do not involve open channels. There are processes that prevent submitting requests to a wide range of employees. The ability to notify an employee about the need to participate in an issue is very important. And notifying a group of employees is essential, as multiple employees may be involved in the issue. At the same time, others do not need to know about it. This function is very important. When claiming integration with messengers, it is necessary to also provide your clients with the ability to use this feature without restrictions.