You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When attempting to create a chat channel from an issue I get
Wait a moment, then try again.
I cannot get past this right now.
Welcome to the community. Sometime there may be some network communication glitches, where after you wait for a while and retry the same operation and everything will work.
However if it is a continuous problem, then you should contact Atlassian Support (https;//support.atlassian.com), so the support team can access the backend logs to further troubleshooting your issues and determine the root cause.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Viasat Inc.
This feels quite durable, and is still happening to me now, so I sense some kind of auth glitch. The questions I have:
* Is there any way to troubleshoot the error more precisely? There's a 500 error occurring.
* Is there any way to fully reset the connection? I have tried uninstalling/reinstalling the chat mechanism but it doesn't seem to do anything for me.
* How can I have some movement on this? The rollout of my process here is blocked by this issue right now.
Thanks!
Gene
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The core of the error is that it's a 500 error but the message (which is functionally false but may be technically true in this specific flow) is that "Issue does not exist or user does not have permission to access the issue). I have full access to the issue and in all other flows the slack integration works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your best option is to contact Atlassian Support, where they have access to the backend system logs to determine the root cause as I suggested before.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.