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.
JIRA Widgets Broke after Update
Hi @Devi_ Gayathri ,
Welcome to the community !!
I believe you are using Jira server Or Data center version and Not Atlassian Cloud instance.
Please shutdown Jira, clear cache and restart. Check if issue still exists.
If yes, then please go through the cause and resolution mentioned in https://confluence.atlassian.com/jirakb/fix-gadget-titles-showing-as-__msg_gadget-in-jira-server-813697086.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Devi_ Gayathri ,
If your instance in Jira server or Data Centre, there are few causes and resoluttions mentioned in https://confluence.atlassian.com/jirakb/fix-gadget-titles-showing-as-__msg_gadget-in-jira-server-813697086.html
Did you try them ? This task should usually be done by Linux/Network teams.
If you are using Jira cloud from Atlassian, then please ocntact atlassian support in https://support.atlassian.com/contact/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian Community!
This error message always means "Jira is not able to reach itself" over the network.
On Cloud it is possible to do this if the network you connect to the internet is doing certain packet-filtering on. You need to talk to your network admins and get them to do some packet tracing.
On Server, packet filtering may also apply, but the usual culprits are broken DNS, broken https certificates, or a firewall on the server that stops it talking to yourself.
Could you tell us what the results of the testing given in the doc Rilwan gave you were? That doc always fixes it for Server if you follow it.
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.