Trying to add a lable to a page for use as a Knowledge Article. I often get this error. GraphQL error: Unexpected HTTP status: 500. Image below.
Hello Mark,
Welcome to Atlassian Community!
The error that you are facing appears to be a known bug where if we click on "Add" without any text on the dialogue or without clicking on the "Create" label first, it will show the GraphQL error.
Please, click on "This affects my team" and also watch to receive updates.
For new labels, please, make sure to click on Create "label-name" first.
Regards,
Angélica
If this is only happening when assigning labels and you do not have any specific App that manages labels than this would be an indicator something on Jira Cloud backends would be wrong.
In case the error persists this is something Atlassian support should look into.
It's a bit tricky as you are on a Free plan that is only entitled to Community support but this kind of annoying error should get sorted out.
Is it still happening now?
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.
Sorry to hear there is still an issue, @Hayrullah Yasar
The initial problems the user reported seem to have been fixed some time ago for Confluence Cloud but it is unclear which product you are referring to.
In case this should be still a problem, I would suggest you describe the issue in a new thread here in Community or contact Atlassian Support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your response. the product is Confluence Cloud.
I have just tried it again now I did not encounter. Maybe it is resolved already.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to Community! Have you looked at the developer console to see where the GraphQL error is pointing to? That will give us a much clearer indication of what's going wrong. Moreover, using a HTTP analyser would be more effective to diagnose the problem in this situation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.