SOLVED: un-assigning unsupported request types, then re-assigning them once supported resolved the issue
hello,
I added a label to ~200 requests with the bulk edit tool in issue navigation. Upon adding a label, an automation ran that assigned a request type to each issue based on the summary text of the issues. Then, once the new request type was set, all of the issues got a message from the Assist App in Slack with the following text:
"This request is no longer connected to Slack, so you can't interact with it here. For updates, go to the request"
Now, when I try to send messages in the thread of those requests, my response is automatically deleted and an Assist App message (only visible to me) is sent explaining that the request is no longer connected to Slack once again.
Because of the disconnection, I am no longer able to support >200 requests through Slack, or by adding comments to the requests in Jira. how can I re-connect these requests ASAP?
Since the disconnection, I have added the automatically assigned request types to the channels I have connected in JSM. Testing sending threaded messages after doing this has resulted in the same automatic deletion of my message. I have also tried re-running the automation assigning one label to each request, with the same result.
I plan on trying a bulk edit of the requests' request type to one standard request type, and will post a comment with information on the results. If it does not work, I will attempt to disconnect JSM from those channels in hopes of being able to respond to these messages. If that also does not work, I'll very likely pivot away from using JSM ASAP to avoid this deeply upsetting issue. any information on how to ensure request disconnection does not happen again under any circumstances would also be greatly appreciated.
