Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

After the update gadget titles don’t show the right names.




JIRA Widgets Broke after Update

2 answers

1 vote
Rilwan Ahmed Community Leader Dec 07, 2022

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

Issue still exists

Rilwan Ahmed Community Leader Dec 15, 2022

Hi @Devi_ Gayathri ,

If your instance in Jira server or Data Centre, there are few causes and resoluttions mentioned in

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

0 votes

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.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events