If you're seeing gadget names such as __MSG_gadget.xxxxxxx there is a knowledge base article How to fix gadget titles showing as __MSG__gadget. If that is what you're seeing, pay careful attention to the Cause section. This explains what changes occured that cause this behavior and can provide additional clues in regards to what you need to change in your network settings, etc.
If the above error is not what you're seeing post a screenshot and we'll take a look.
Just to explain that __MSG__gadget comment in short (the doc doesn't really summarise it) - your JIRA needs to be able to talk to itself. It's as though the gadgets are running on another server. You get this error when the server that is running the gadgets can't reach the server giving it data. In this case, they're both the same JIRA, so you need to ensure the JIRA can see itself.
The usual culprit is SSL and proxies - JIRA will run fine when protected by SSL certtificates, but throw this error when its own gadgets are refused access to the JIRA server because you've not imported the certificates!
You did say "name of the gadget", not fields.
The __msg__ thing happens on the dashboard and in the list of gadgets.
I don't know what you mean by "brown", as there is no screenshots attached. If it's not the _msg_ thing, you are going to need to explain more (ideally with a screenshot so there's no misunderstanding)
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs