This is not a bugfix! It may solve the problem of a few people, but it makes the use of the wallboard function impossible for thousands of paying customers.

You should be ashamed to deliver something like this and charge money for it. That's unbelievable impudence! 

How many votes does an issue need to be addressed? 

I'm very frustrated by this issue. My wallboards are kind of useless without the context of a title to show the users what they are looking at. The workaround is not helpful in this instance. 

I can also add a plus one for the request that all gadgets have a title - if I can't show clearly on a cycling slideshow which graph relates to which project/filter then the data is meaningless for my team

Just ran into this as well...   The more I use Jira/Service Desk and Confluence, the more frustrated I get with how little Atlassian seems to care about their products and customers.

This is one of many examples of a feature which would be useful if it had been fully implemented. **But it's not.

Everyone who tries to display a wallboard expects it to have the same information as the underlying dashboard. But it doesn't.

This renders the feature useless. 

It's very difficult to understand why Atlassian ignores such obvious product defects, reported by paying customers, with such impunity. It's a little like buying a car.  You see it has a turn signal stalk on the steering wheel, and it has lights on all four corners.  Only after you've bought it does it become apparent that the turn signals only work for left turns, not for right turns.  The car manufacturer's position is "Not enough votes have been received by prospective right turners to consider fixing this." Seriously ? I would be ashamed to work for a company that treated paying customers like this.

The lack of titles renders wallboards useless.

No wallboard in our office due to this missing feature (more a bug fixed btw)

Any news about this?

The priority needs to be HIGH on this one, please. Having no context for the data on the wallboard makes absolutely no sense at all. We need to know what we're looking at when we see the filters on the wallboard and the Rich Text Gadget is useless since it magically disappears on the wallboard.

Would be great to have that added. We would like to display a wallboard consisting of all of our service desks. Currently there is no way to tell the desks apart. The internet suggests to use the text gadget. However that was removed with the recommendation of the Rich Text Gadget. This is not shown on the wallboard. So this is no solution at all.

This needs to be fixed ASAP. 

Wallboards are useless without being able to display titles. Please correct this problem.

Wallboard is useless without this feature bug fixed.

18 months minimum for something as simple as a title, and no resolution. Sometimes, I have to question the value of this product. 

Hi Team, Please fix this issue soon. 

Added my vote - the Wallboard feature is useless without this.

Could you please fix this bug? Is there reasoning why you wouldnt show what the graph you're looking at on the wallboard is about? This makes the whole wallboard feature pretty useless....

A terrible workaround would be to enable the text gadget which also makes JIRA vulnerable to XSS attacks (also a reported bug: JRA-21965)

We love the Wallboard feature but this open issue is preventing us from using it at all.  

If you want this to be fixed remember to vote for it!

Two of our customers have asked about this functionality recently. I am keeping my fingers crossed that this will be implemented in a not so distant future!

I don't agree with the occurrence factor for this case. This seems a common pattern I have seen with other issues/suggestions Atlassian customers report. Perhaps Nick is correct; the feature is not regularly used because it isn't finished yet?

In my view this problem affects 100% of the people that try this feature. Except for very small customers/teams with trivial situations I think this defect would be a problem for anyone using a Wallboard.

"Occurrence Factor: 25% - affects a minority of users or feature is not regularly used"

Is it possible, the reason it's not regularly used is that it's not very useful in its current state.