• 18
    • 15
    • Hide
      Atlassian Update – 15 February 2018

      Hi everyone,

      Thanks for your interest in this issue.
      This request is considered a potential addition to our longer-term roadmap.

      We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

      For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:

      • Performance and stability improvements
      • Archiving projects for improved performance
      • Optimising the use of custom fields
      • Improving performance of boards
      • Improving Jira notifications
      • Allowing users to edit shared filters and dashboards
      • Mobile app for Jira Server

      You can learn more about our approach to highly voted server suggestions here.

      To learn more on how JAC suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 15 February 2018 Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server You can learn more about our approach to highly voted server suggestions here . To learn more on how JAC suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Hi,

      Jira users in my company report that the Project Summary page does not show all charts they would like to see. I have suggested that they could create a dashboard containing all relevant charts, but they complain that they cannot name the gadgets as they would like.

      For example the chart which is presented as 'Issues: 30 Day Summary' at the Project Summary page, could be placed at the dashboard, but its name is set to 'Created vs Resolved Chart: <Project Name>'. That would be great if users could edit the title.

      Thank you,
      Lukasz

            [JRASERVER-19766] Editing gadget titles

            Tom Hallam added a comment -

            14 years and counting....

            Tom Hallam added a comment - 14 years and counting....

            Kulgaurav Kanade added a comment - - edited

            Its baffling how this wasn't thought of during the baseline release. End customer or non-technical stakeholders are confused by JQL filters showing up as a widget title. 

            Kulgaurav Kanade added a comment - - edited Its baffling how this wasn't thought of during the baseline release. End customer or non-technical stakeholders are confused by JQL filters showing up as a widget title. 

            aerochaz added a comment -

            I'll vote for this feature to be added. We have multiple users that would benefit from this.

            aerochaz added a comment - I'll vote for this feature to be added. We have multiple users that would benefit from this.

            We need this!

            Dani Miles added a comment - We need this!

            Would love to be able to do this as it has been implemented for quite some time in the cloud version....shame as you can use the same filter with different attributes and get different numbers in the charts without the ability to account for the discrepancy in the gadget title. For instance I have one chart that shows all subtasks and their owners, then I use the same filter but this time use the labels to show what team the ticket belongs to. Not all subtasks get a label as there are two levels of subtask  

            Paul Davis added a comment - Would love to be able to do this as it has been implemented for quite some time in the cloud version....shame as you can use the same filter with different attributes and get different numbers in the charts without the ability to account for the discrepancy in the gadget title. For instance I have one chart that shows all subtasks and their owners, then I use the same filter but this time use the labels to show what team the ticket belongs to. Not all subtasks get a label as there are two levels of subtask  

            This is ridiculous! the ticket has been filed for long time ago, technically speaking it shouldn't take much effort to implement, so it's obvious it's strategical decision why this hasn't been implemented.

            Nawasreh, Aladdin added a comment - This is ridiculous! the ticket has been filed for long time ago, technically speaking it shouldn't take much effort to implement, so it's obvious it's strategical decision why this hasn't been implemented.

            Sean M added a comment -

            Not surprised. It never will be added either. Go buy the cloud version if you want to keep using Jira. Mind you, if you're 'cool' with running in the cloud, you really oughta look at some other options...

            Sean M added a comment - Not surprised. It never will be added either. Go buy the cloud version if you want to keep using Jira. Mind you, if you're 'cool' with running in the cloud, you really oughta look at some other options...

            It is completely unacceptable that this feature has not been added. 

            Andrew Gross added a comment - It is completely unacceptable that this feature has not been added. 

            Hi Team,

             

            Could you please let us know by when we can expect this to get implemented on the Server version.

            Any update would be highly appreciated.

             

            sujata birajdar added a comment - Hi Team,   Could you please let us know by when we can expect this to get implemented on the Server version. Any update would be highly appreciated.  

            Hello, can you pleaaaase implement this?

            It would be so helpfull to our users!

            In Fryslan we say: "Baarne sjoeke Baarne!!"

            RaymondMeer added a comment - Hello, can you pleaaaase implement this? It would be so helpfull to our users! In Fryslan we say: "Baarne sjoeke Baarne!!"

            Wow 11 years for such a simple request - please implement.

            Bryan Kapustka added a comment - Wow 11 years for such a simple request - please implement.

            Yes, Go for it. Or as we say in Swedish --KBK! Kör Bara Kör! – "Just drive!"

            Niklas Gotting added a comment - Yes, Go for it. Or as we say in Swedish --KBK! Kör Bara Kör! – "Just drive!"

            Seriously Atlassian - two years ago you said this would take 12 months to review. I mean you've already done it for Jira Cloud, right? So that tells me you know how to do it, you just can't be bothered to do it for those of us who prefer to remain on Jira Server. Simply not good enough. I feel like the poor relation here - we're not on Server because we're too dumb to understand Cloud, we're on server because we have good solid reasons to choose that deployment model over Cloud at this time.

            So how about some action?

            Andrew Ball added a comment - Seriously Atlassian - two years ago you said this would take 12 months to review. I mean you've already done it for Jira Cloud, right? So that tells me you know  how to do it, you just can't be bothered to do it for those of us who prefer to remain on Jira Server. Simply not good enough. I feel like the poor relation here - we're not on Server because we're too dumb to understand Cloud, we're on server because we have good solid reasons to choose that deployment model over Cloud at this time. So how about some action?

            Low hanging fruit!

            Nick DePrizio added a comment - Low hanging fruit!

            Hey Atlassian, can't recognize, why you enable features only in one line of your product (here the cloud-line) but not in the other (here server-line). Is it that complicate to incorporate it in server-line too? When you decide to integrate this feature in the cloud-line, then you are probably convinced it's a benefit for your (cloud-line)users. Do you think your server-line-users are that different from the cloud-ones, that they would notice the implementation as a disadvantage if you do it without being asked for?

            Will never understand your policy regarding the implement of features. To me your product unfortunately (and unnecessarily) lacks too many features, your costumers askin for (watch all the issues in here). But instead of takin them constantly into your product (in server- AND cloud-line), you make some fancy colorchanges and other stuff or only implement them in only one productline. Strange behaviour but maybe down under clocks turn the other way.....

            Or maybe you wanna give a peace of the cake to all those vendors deliverin' plenty of plugins to refit the features you have declined to implement or you are undetermined to implement?

            Stefan Nahr added a comment - Hey Atlassian, can't recognize, why you enable features only in one line of your product (here the cloud-line) but not in the other (here server-line). Is it that complicate to incorporate it in server-line too? When you decide to integrate this feature in the cloud-line, then you are probably convinced it's a benefit for your (cloud-line)users. Do you think your server-line-users are that different from the cloud-ones, that they would notice the implementation as a disadvantage if you do it without being asked for? Will never understand your policy regarding the implement of features. To me your product unfortunately (and unnecessarily) lacks too many features, your costumers askin for (watch all the issues in here). But instead of takin them constantly into your product (in server- AND cloud-line), you make some fancy colorchanges and other stuff or only implement them in only one productline. Strange behaviour but maybe down under clocks turn the other way..... Or maybe you wanna give a peace of the cake to all those vendors deliverin' plenty of plugins to refit the features you have declined to implement or you are undetermined to implement?

            Hi everyone,

            Thanks for your interest in this issue.
            This request is considered a potential addition to our longer-term roadmap.

            We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

            For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:

            • Performance and stability improvements
            • Archiving projects for improved performance
            • Optimising the use of custom fields
            • Improving performance of boards
            • Improving Jira notifications
            • Allowing users to edit shared filters and dashboards
            • Mobile app for Jira Server

            You can learn more about our approach to highly voted server suggestions here.

            To learn more on how JAC suggestions are reviewed, see our updated workflow for server feature suggestions.

            Kind regards,
            Jira Server Product Management

            Jakub Lazinski (Inactive) added a comment - Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server You can learn more about our approach to highly voted server suggestions here . To learn more on how JAC suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management

            YES!! Please continue to thrill your customers by updating the Server version to enable the editing of Gadget titles!!

            Jennie Rodrigues added a comment - YES!! Please continue to thrill your customers by updating the Server version to enable the editing of Gadget titles!!

            I agree with Azfar, it wil also bring glittery eyes to our server-version users and sprinkles on top!

            RaymondMeer added a comment - I agree with Azfar, it wil also bring glittery eyes to our server-version users and sprinkles on top!

            Saw that the Cloud already got this feature enabled. Please please please push it to Server version!! It would bring sunshine and rainbows to us server users.

            Azfar Masut added a comment - Saw that the Cloud already got this feature enabled. Please please please push it to Server version!! It would bring sunshine and rainbows to us server users.

            Hi Atlassian

            I am hoping to get the option of renaming my gadgets since I started using JIRA.

            It will be great, if you can provide this Naming option for gadgets in JIRA server as soon as possible.

            Deeptendra Chakraborty added a comment - Hi Atlassian I am hoping to get the option of renaming my gadgets since I started using JIRA. It will be great, if you can provide this Naming option for gadgets in JIRA server as soon as possible.

            Dear Atlassian,

            could you give your Server customers an update on this case? I see the corresponding issue for JIRA Cloud JRACLOUD-19766 was updated as resolved yesterday. I'm sure all the voters and watchers on this case would like to know when you plan to release the changes for Server.

            I would like to hear a cogent explaination why the issue (JRACLOUD-19766) was addressed in JIRA Cloud first when there are more votes and more watchers on the issue for JIRA Server (JRASERVER-19766)...

            Cheers,
            Dwight

            Dwight Holman added a comment - Dear Atlassian, could you give your Server customers an update on this case? I see the corresponding issue for JIRA Cloud JRACLOUD-19766 was updated as resolved yesterday. I'm sure all the voters and watchers on this case would like to know when you plan to release the changes for Server. I would like to hear a cogent explaination why the issue ( JRACLOUD-19766 ) was addressed in JIRA Cloud first when there are more votes and more watchers on the issue for JIRA Server ( JRASERVER-19766 )... Cheers, Dwight

            +1, JIRA Cloud user.

            Properly describing a gadget's content is very important, otherwise it loses its value.

            I see it from my team perspective, first time they see the dashboard I'm just creating they'll prob. ask:

                What does this "Issue Statistics: Filter: eCommerce BAU Assigned (Assignee)" box contain?

            I would tell them, is the "Assigned and Open Issues per Developer" stats, the problem is that they will prob. ask again next time 

             

             

             

            Jorge Pablos added a comment - +1, JIRA Cloud user. Properly describing a gadget's content is very important, otherwise it loses its value. I see it from my team perspective, first time they see the dashboard I'm just creating they'll prob. ask:     What does this "Issue Statistics: Filter: eCommerce BAU Assigned (Assignee)" box contain? I would tell them, is the "Assigned and Open Issues per Developer" stats, the problem is that they will prob. ask again next time       

            It's so interesting to see how many users agree on issues that affect them. Has there been any feedback from Atlassian? 

            This would be great for our team!

            Maria Chacon Brito added a comment - It's so interesting to see how many users agree on issues that affect them. Has there been any feedback from Atlassian?  This would be great for our team!

            Hell yes - when you have many heatmaps for instance when tracking risks - it would be great to see which one is inherent/current/target etc.

             

            Its just a clarity thing for users, this is basic functionality that would be good to have.

            Alex Lawrence added a comment - Hell yes - when you have many heatmaps for instance when tracking risks - it would be great to see which one is inherent/current/target etc.   Its just a clarity thing for users, this is basic functionality that would be good to have.

            V7.3.0 has also the problem.

            Christian Sprenger added a comment - V7.3.0 has also the problem.

            +1 on this Feature

            Kani Kumaran added a comment - +1 on this Feature

            It would be really nice to have this, we can't easily communicate what things mean in the dashboard to new folks on our team. If this feature were implemented, we would be able to easily label the gadgets in our dashboards.

            Taylor Jones added a comment - It would be really nice to have this, we can't easily communicate what things mean in the dashboard to new folks on our team. If this feature were implemented, we would be able to easily label the gadgets in our dashboards.

            +1 on this feature.  I really expected that being able to edit a gadget title on my dashboard would have been there.  I'm constantly answering the question "What does this gadget tell me again?"  Being able to edit the title or even better ability to add a longer description we can see when hovering over a "?" icon or somthing would be awesome.  "Two Dimensional Filter Statistic: [query name]" really does not tell me anyting.  Having a pie chart title say Pie is wasteful.  We can tell what type of gadget it is by looking at it.  I'm staring at a pie chart, why have pie chart in the title?

            Dale Bronk added a comment - +1 on this feature.  I really expected that being able to edit a gadget title on my dashboard would have been there.  I'm constantly answering the question "What does this gadget tell me again?"  Being able to edit the title or even better ability to add a longer description we can see when hovering over a "?" icon or somthing would be awesome.  "Two Dimensional Filter Statistic: [query name] " really does not tell me anyting.  Having a pie chart title say Pie is wasteful.  We can tell what type of gadget it is by looking at it.  I'm staring at a pie chart, why have pie chart in the title?

            Hi Dave,

            is nice to have some kind of comment from Atlassian. My experience as a customer is that we get the same kind of answer to a range of suggestions across different product areas, e.g.

            Clearly areas that are used by many customers.

            As a large organisation you guys need to get better at "walking while chewing gum". That is - doing strategic stuff AND responding to customer requests. Remember that the strategic stuff might not matter much to existing customers - since they already bought the product.

            As you noted; the ability for add-on developers to create custom gadgets is nice but so far my searching has not resulted in a 3rd party gadget that address this.

            In a fit of enthusiasm I downloaded the source code for JIRA to investigate customizing some of the existing gadgets I discovered even unzipping the sources on a Windows PC wasn't possible (due to the length of path/file names). So I'd need to find a Mac or Linux box to do that on apparently...

            My vote would be switch the effort/time spent on live streams/summits into basic product improvements. i.e. something that end users will benefit from every day they use the product.

            Cheers,
            Dwight

            Dwight Holman added a comment - Hi Dave, is nice to have some kind of comment from Atlassian. My experience as a customer is that we get the same kind of answer to a range of suggestions across different product areas, e.g. kanban boards improvements JSW-6175 (4 years) the operation of sprints in Agile boards JSW-10805 (2 years) Problems in Sprint reports JSW-11354 , JSW-10292 Clearly areas that are used by many customers. As a large organisation you guys need to get better at "walking while chewing gum". That is - doing strategic stuff AND responding to customer requests. Remember that the strategic stuff might not matter much to existing customers - since they already bought the product. As you noted; the ability for add-on developers to create custom gadgets is nice but so far my searching has not resulted in a 3rd party gadget that address this. In a fit of enthusiasm I downloaded the source code for JIRA to investigate customizing some of the existing gadgets I discovered even unzipping the sources on a Windows PC wasn't possible (due to the length of path/file names). So I'd need to find a Mac or Linux box to do that on apparently... My vote would be switch the effort/time spent on live streams/summits into basic product improvements. i.e. something that end users will benefit from every day they use the product. Cheers, Dwight

            Dave Meyer added a comment -

            Hi ykaldirim1390552773,

            The JIRA product management team tracks this (and all) requests on jira.atlassian.com. You can read our post on how we use jira.atlassian.com. While votes do matter (and you can watch the Atlassian Summit livestream next week to hear us announce how many votes we've resolved this year ) we invest in strategic themes or areas of the product. On top of that, adding new features or more configuration options to existing features is only one small part of our development effort for JIRA – we also need to fix bugs, improve performance, improve the user interface, help new users get started, invest in scalability for large deployments, and make investments in our engineering health and infrastructure to sustain everything else.

            Unfortunately dashboard UI and configurability is not a place where we have been able to invest in the last couple years; however we have made significant performance improvements to many of the most popular gadgets to improve dashboard page load times, and added the ability for add-on developers to provide custom gadgets in JIRA Cloud. While we don't have any immediate plans to focus on dashboards right now, rest assured that we are listening and doing our best to prioritize this request against the hundreds of others in the JRA, JSW, and JSD projects that have similar numbers of votes.

            Dave Meyer
            JIRA Product Management

            Dave Meyer added a comment - Hi ykaldirim1390552773 , The JIRA product management team tracks this (and all) requests on jira.atlassian.com. You can read our post on how we use jira.atlassian.com . While votes do matter (and you can watch the Atlassian Summit livestream next week to hear us announce how many votes we've resolved this year ) we invest in strategic themes or areas of the product. On top of that, adding new features or more configuration options to existing features is only one small part of our development effort for JIRA – we also need to fix bugs, improve performance, improve the user interface, help new users get started, invest in scalability for large deployments, and make investments in our engineering health and infrastructure to sustain everything else. Unfortunately dashboard UI and configurability is not a place where we have been able to invest in the last couple years; however we have made significant performance improvements to many of the most popular gadgets to improve dashboard page load times, and added the ability for add-on developers to provide custom gadgets in JIRA Cloud. While we don't have any immediate plans to focus on dashboards right now, rest assured that we are listening and doing our best to prioritize this request against the hundreds of others in the JRA, JSW, and JSD projects that have similar numbers of votes. Dave Meyer JIRA Product Management

            I agree with some of the other comments - this seems to be a simple and obvious configuration option (improvement) to help users and business get better value out of the product. Ironic that this simple option is not available in a product with so much complex customization built-in. Sadly, from reading the comment history I do not hold much hope of this being done soon.

            For those interested in this one you might want to check out (and vote for) JRA-60152 too - for anyone that wants to use Wallboards that seems worse than this one. You might find that less depressing to visit since it was only logged this year It's not directly linked to this one but IMHO is related.

            Dwight Holman added a comment - I agree with some of the other comments - this seems to be a simple and obvious configuration option (improvement) to help users and business get better value out of the product. Ironic that this simple option is not available in a product with so much complex customization built-in. Sadly, from reading the comment history I do not hold much hope of this being done soon. For those interested in this one you might want to check out (and vote for) JRA-60152 too - for anyone that wants to use Wallboards that seems worse than this one. You might find that less depressing to visit since it was only logged this year It's not directly linked to this one but IMHO is related.

            +1 We would really appreciate this resolved

            matt kaiser added a comment - +1 We would really appreciate this resolved

            Hi,

            This topic is opened 7 "seven" years ago. Is there anybody hearing more than 150 people? How many votes you need to develop something? I believe you will see such votes if you share with us. Where is JIRA product owner? * If JIRA team doesn't care users , you may close suggestion part.  *

            Yunus KALDIRIM added a comment - Hi, This topic is opened 7 "seven" years ago . Is there anybody hearing more than 150 people? How many votes you need to develop something? I believe you will see such votes if you share with us. Where is JIRA product owner? * If JIRA team doesn't care users , you may close suggestion part.  *

            +1
            Really frustrating to see such simple changes taking so long and total apathy from Atlassian in addressing it.

            Vishal Gautam added a comment - +1 Really frustrating to see such simple changes taking so long and total apathy from Atlassian in addressing it.

            Anil Kumar added a comment -

            +1 Vote
            Waiting for an update from long on this.

            Anil Kumar added a comment - +1 Vote Waiting for an update from long on this.

            +1 vote. Our users include non-technical business-people who wants to see a title and not a gadget-name.

            Carsten Beck-Astrup added a comment - +1 vote. Our users include non-technical business-people who wants to see a title and not a gadget-name.

            Erin Truax added a comment -

            +1 vote here.

            This seems to be a relatively easy thing to add, yet issues have been open on it for 5 years. Not having customizable titles for widgets makes dashboards really difficult to use!

            Erin Truax added a comment - +1 vote here. This seems to be a relatively easy thing to add, yet issues have been open on it for 5 years. Not having customizable titles for widgets makes dashboards really difficult to use!

            Jira has a long list of low hanging fruit issues that doesn't belong in a commercially supported product. If this was a free open source product it'd be one thing, but seeing in some cases trivial functionality bugs being open for years, like this one from 2011: JRA-24671 really sours the customer experience.

            Now apparently we're needing another, entirely reasonable, "suggestion" which brings functionality to the various gadgets. And it's been open since 2009.
            Your product doesn't work without this functionality. It's like selling a car with square wheels, and calling requests for round wheels a "suggestion".

            Nick Vaernhoej added a comment - Jira has a long list of low hanging fruit issues that doesn't belong in a commercially supported product. If this was a free open source product it'd be one thing, but seeing in some cases trivial functionality bugs being open for years, like this one from 2011: JRA-24671 really sours the customer experience. Now apparently we're needing another, entirely reasonable, "suggestion" which brings functionality to the various gadgets. And it's been open since 2009. Your product doesn't work without this functionality. It's like selling a car with square wheels, and calling requests for round wheels a "suggestion".

            +1.
            The extra words like "Filter Results", "2 Dimensional Filter Statistics"
            1. Adds no value (who cares what type of filter it is),
            2. Looks unprofessional
            3. Consumes real estate on the widget for no reason

            This issue should have been fixed a long long time ago.

            Raj Ramanatha added a comment - +1. The extra words like "Filter Results", "2 Dimensional Filter Statistics" 1. Adds no value (who cares what type of filter it is), 2. Looks unprofessional 3. Consumes real estate on the widget for no reason This issue should have been fixed a long long time ago.

            nikhil1611 added a comment -

            +1 .. upvote .. it is needed now.

            nikhil1611 added a comment - +1 .. upvote .. it is needed now.

            I'm also adding +1 to this topic. It's really easy to add simple title to gadgets.

            Yunus KALDIRIM added a comment - I'm also adding +1 to this topic. It's really easy to add simple title to gadgets.

            Anil Kumar added a comment -

            Thanks Rashi for followup, Looking for any message/timeline from PM team.

            Anil Kumar added a comment - Thanks Rashi for followup, Looking for any message/timeline from PM team.

            Rashi Saxena added a comment - - edited

            Is there any progress on this one?

            I need to have this for my project and my gadgets are showing "2 dimensional ---" on the heading, which is quite meaningless for the mangers.

            Rashi Saxena added a comment - - edited Is there any progress on this one? I need to have this for my project and my gadgets are showing "2 dimensional ---" on the heading, which is quite meaningless for the mangers.

            This was a nice to have until we upgraded to v6.4.11 and it now moved up in priority for me.

            I have a several Two Dimensional Filter Statistics with different filters and before it would include the filter name in the title. It wasn't perfect (I would have preferred to override the title) but I could differentiate the two tables. But now it just lists the gadget name and one of the dimensions: "Two Dimensional Filter Statistics by Priority".

            Perhaps I should post a bug for the change in behavior.

            tom-cassiotis-cwi added a comment - This was a nice to have until we upgraded to v6.4.11 and it now moved up in priority for me. I have a several Two Dimensional Filter Statistics with different filters and before it would include the filter name in the title. It wasn't perfect (I would have preferred to override the title) but I could differentiate the two tables. But now it just lists the gadget name and one of the dimensions: "Two Dimensional Filter Statistics by Priority". Perhaps I should post a bug for the change in behavior.

            I'm adding my vote to this issue. Titles on the gadgets are a must. I am using the same gadget multiple times to display different info, but I have no way of distinguishing what is being shown, except to Edit the gadget to see how I set it up. Even the ability to add a comment to the gadget would be helpful.

            Karen DuBrucq added a comment - I'm adding my vote to this issue. Titles on the gadgets are a must. I am using the same gadget multiple times to display different info, but I have no way of distinguishing what is being shown, except to Edit the gadget to see how I set it up. Even the ability to add a comment to the gadget would be helpful.

            Yggy King added a comment -

            Seems strange and silly that titles are not configurable. Obviously I don't know your codebase, but it seems like such a simple thing.

            Yggy King added a comment - Seems strange and silly that titles are not configurable. Obviously I don't know your codebase, but it seems like such a simple thing.

            Hi daniel159

            Please refer to this bug ticket regarding the issue you are facing :

            Adrian Stephen added a comment - Hi daniel159 Please refer to this bug ticket regarding the issue you are facing : https://jira.atlassian.com/browse/JRA-44824

            OLD-DANIEL added a comment -

            Dashboard without clear titles are a bit useless.
            I added a pie chart and i does not even show the selected filter name instead it is written: JQL query

            OLD-DANIEL added a comment - Dashboard without clear titles are a bit useless. I added a pie chart and i does not even show the selected filter name instead it is written: JQL query

            Any updates on this? We have feedback from our dashboard viewers that, better titles would definitely help.
            To start with; something similar to "Text" Gadget without the HTML would do.

            Harsh Mohta added a comment - Any updates on this? We have feedback from our dashboard viewers that, better titles would definitely help. To start with; something similar to "Text" Gadget without the HTML would do.

            mcbridejc added a comment -

            This really seems like a no brainer. Dashboard widgets need a better description of what they are than the widget type (especially when two widgets of the same type can show very different things on the dashboard).

            mcbridejc added a comment - This really seems like a no brainer. Dashboard widgets need a better description of what they are than the widget type (especially when two widgets of the same type can show very different things on the dashboard).

            Hi Atlassian,

            I need the same facility to improve the view of our reports.

            I am recently using a plugin called "Custom Content for JIRA" from "TNG Technologies" which helps to display a webpage or image on the dashboard. In that I have an option to change the gadget title as per my wish. That was awesome. We need that exact functionality in all other gadgets.

            This is the major requirement for the Dashboard reports.Please rectify it as soon as possible.

            Thank you

            S. Ravi Venkatramana added a comment - Hi Atlassian, I need the same facility to improve the view of our reports. I am recently using a plugin called "Custom Content for JIRA" from "TNG Technologies" which helps to display a webpage or image on the dashboard. In that I have an option to change the gadget title as per my wish. That was awesome. We need that exact functionality in all other gadgets. This is the major requirement for the Dashboard reports.Please rectify it as soon as possible. Thank you

            Atlassian, please close this issue or give some feedback. It's reported on 2009, if you not have a decision in five and a half year, then maybe you should say no or suggest a solution and plan it for some future release.

            Johan Hallin added a comment - Atlassian, please close this issue or give some feedback. It's reported on 2009, if you not have a decision in five and a half year, then maybe you should say no or suggest a solution and plan it for some future release.

            Giulia O. added a comment -

            Hello everybody,
            my team and myself are also quite interested in this feature. Any update?

            Giulia O. added a comment - Hello everybody, my team and myself are also quite interested in this feature. Any update?

            Any updates on this issue from atlassian??

            RaymondMeer added a comment - Any updates on this issue from atlassian??

            M added a comment -

            Hi there,
            Same remarks from customers, it is not very 'sexy' to have everywhere those title, we know that it is a resulf filter gadget or bidimensionnal, it it a bit confusing with the title of the filter....
            Thanks !

            M added a comment - Hi there, Same remarks from customers, it is not very 'sexy' to have everywhere those title, we know that it is a resulf filter gadget or bidimensionnal, it it a bit confusing with the title of the filter.... Thanks !

            +1, also placed my vote on this issue.

            In a recent presentation, our customer was delighted with JIRA dashboards but unhappy about the gadget titles, stating they would draw attention away from the content and hamper the goal of presenting concise, no-fuss management information.

            This feature would be greatly appreciated!

            Tobias Babin added a comment - +1, also placed my vote on this issue. In a recent presentation, our customer was delighted with JIRA dashboards but unhappy about the gadget titles, stating they would draw attention away from the content and hamper the goal of presenting concise, no-fuss management information. This feature would be greatly appreciated!

            Peter Wu added a comment -

            Agreed!

            Peter Wu added a comment - Agreed!

            Frank Stillone added a comment - - edited

            Agreed!

            I have a large number of filters and I am finding that I have to use a naming conventions so that sorting allows me to group them by project however when these filter names get used as titles in gadgets on dashboards, users who have little technical input into the relevant JIRA project find the title of little relevance as it does not really describe what the chart or table is representing.

            It would be great to get an update here from Atlassian as to what is being done about this,

            Thanks!

            Frank Stillone added a comment - - edited Agreed! I have a large number of filters and I am finding that I have to use a naming conventions so that sorting allows me to group them by project however when these filter names get used as titles in gadgets on dashboards, users who have little technical input into the relevant JIRA project find the title of little relevance as it does not really describe what the chart or table is representing. It would be great to get an update here from Atlassian as to what is being done about this, Thanks!

              Unassigned Unassigned
              f31790979e99 Lukasz Guminski
              Votes:
              373 Vote for this issue
              Watchers:
              197 Start watching this issue

                Created:
                Updated: