Assist is not two-way syncing created issues to Slack

Question

For at least two of our JSM projects the Assist Chat integration in Slack is not relaying issues created in Jira back to the Agent Channels.

We have noticed some other wonkiness since the deprecation of Halp, like the automatic ticket creation emoji changing from the lightning bolt :zap: to the regular :ticket: and that Slack group names in messages are rendered with their !subteam ID.

Those are not a big deal, but we rely on the two way sync from Jira to Slack to maintain visibility for new issues.

Is anyone else noticing this issue? Is there any advice for mitigating it?

Thanks!

Gaurav_baplr5 · Answer

Hi Team,

if you are still loooking for 3rd party https://slackjira.com/  
provides all features of Assist / Halp with lesser pricing.

You can get your custom emoji to create and relay information to and from Slack to Jira/JSM

You can also set custom / correct reporter/assign based on rules .

Feel free to message me /reply for any issues

Bob Shields · Answer

We have noticed a similar issue when setting a new reporter on an issue. The request is not routed to the new reporter in Assist in Slack. This means a third party automation can't be used to raise a request and then set the correct reporter so that they can communicate via Slack. The new reporter has to go into the Jira portal.

We get the same error message: "Something unexpected went wrong. This comment could not be added to the issue."

Antônio Augusto Sousa Britto · Answer

I've noticed since Halp shutdown that the issues are no sync'd back with Slack when we move them to different squad projects. Hence, the team cannot communicate with the requester through ticket messages. And this message keeps popping on the thread that originates the issue:

"Something unexpected went wrong. This comment could not be added to the issue."