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

Devi_ Gayathri December 7, 2022

Capture.PNG

 

 

JIRA Widgets Broke after Update

2 answers

1 vote
Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 7, 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 https://confluence.atlassian.com/jirakb/fix-gadget-titles-showing-as-__msg_gadget-in-jira-server-813697086.html

Devi_ Gayathri December 14, 2022

Issue still exists

Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 15, 2022

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/

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 14, 2022

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