• 0
    • 3
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Now that gadgets and reports are both implemented as plugins, it should be possible to make them interchangeable, differing in just which view is used to render them. This would allow users to put any of the reports (popular issues, timetracking, workload, roadmap, changelog) to be placed on the dashboard.

            [JRACLOUD-4916] Make gadgets and reports interchangeable

            I'd really like to see this feature implemented!

            Han Geerligs added a comment - I'd really like to see this feature implemented!

            I definitely vote for this one

            I Gede Panca Sutresna added a comment - I definitely vote for this one

            Peter Merel added a comment - - edited

            It is simply incredible that after all these years I still cannot add a report to a dashboard via a gadget. I and every jira user just wants a non-classic cumulative flow diagram to paste up on the wallboard. You guys are seriously telling me I have to scrape the thing into an iframe and bodgy it together with spakfiller?

            If so then, really, that's just nuts.

            Peter Merel added a comment - - edited It is simply incredible that after all these years I still cannot add a report to a dashboard via a gadget. I and every jira user just wants a non-classic cumulative flow diagram to paste up on the wallboard. You guys are seriously telling me I have to scrape the thing into an iframe and bodgy it together with spakfiller? If so then, really, that's just nuts.

            I'd like this too. I just finished writing my first custom report and my users want to embed that report into a dashboard. Reason being, the data produced by the report is a set of metrics based on the subtasks and linked issues related to a set of user stories. My users need half-a-dozen instances of the Issue Statistics chart to generate the data that's contained in my custom report.

            Logan G Hawkes added a comment - I'd like this too. I just finished writing my first custom report and my users want to embed that report into a dashboard. Reason being, the data produced by the report is a set of metrics based on the subtasks and linked issues related to a set of user stories. My users need half-a-dozen instances of the Issue Statistics chart to generate the data that's contained in my custom report.

            I think it's a must have feature

            Arsenty Karamurza added a comment - I think it's a must have feature

            We live and die by our dashboards and certain reports would be lovely to see there. In particular, we would really like the "summary" part of the "Version Workload" report to be a portlet, as it allows us to very quickly understand which developers have "spare time" when we are triaging incoming customer support issues.

            Sebastian Good added a comment - We live and die by our dashboards and certain reports would be lovely to see there. In particular, we would really like the "summary" part of the "Version Workload" report to be a portlet, as it allows us to very quickly understand which developers have "spare time" when we are triaging incoming customer support issues.

            ChristineA added a comment -

            I also would like to have this one implemented. Eg: the Single Level Group By report would be very convenient to fit in a dashbaord page. So, I've voted for this one.

            ChristineA added a comment - I also would like to have this one implemented. Eg: the Single Level Group By report would be very convenient to fit in a dashbaord page. So, I've voted for this one.

            We'd like this too. Because our releases are not very frequent, we can end up with a lot of issues logged against a project, which makes it difficult to see what the major components of the release are. We're fixing this by creating a 'Deliverable' issue type that will be linked to the actual work items/bugs/etc. People can then get a "high-level" roadmap by doing a Single Level Group By report on a filter that shows only that issue type. It would be convenient to be able to save that report as a new dashboard tab.

            Richard Fine added a comment - We'd like this too. Because our releases are not very frequent, we can end up with a lot of issues logged against a project, which makes it difficult to see what the major components of the release are. We're fixing this by creating a 'Deliverable' issue type that will be linked to the actual work items/bugs/etc. People can then get a "high-level" roadmap by doing a Single Level Group By report on a filter that shows only that issue type. It would be convenient to be able to save that report as a new dashboard tab.

            We are also in bad need of this, or solution that might work to achieve displaying Roadmap, or Risk Management panels to be embedded in Atlassian's Confluence Wiki. We have both (three, if I count Bamboo), and this is a must for dealing with projects in our company...

            thanks,
            Mike

            Deleted Account (Inactive) added a comment - We are also in bad need of this, or solution that might work to achieve displaying Roadmap, or Risk Management panels to be embedded in Atlassian's Confluence Wiki. We have both (three, if I count Bamboo), and this is a must for dealing with projects in our company... thanks, Mike

            AntonA added a comment -

            Asgeir,

            Thanks for the info. What we need is a way to request only the report's output, and not the surrounding HTML. Portlets have the RunPortlet action that does this (spits out only portlets HTML and not the whole Dashboard). We need a "RunReport" WebWork action.

            Anton

            AntonA added a comment - Asgeir, Thanks for the info. What we need is a way to request only the report's output, and not the surrounding HTML. Portlets have the RunPortlet action that does this (spits out only portlets HTML and not the whole Dashboard). We need a "RunReport" WebWork action. Anton

              Unassigned Unassigned
              7ee5c68a815f Jeff Turner
              Votes:
              38 Vote for this issue
              Watchers:
              27 Start watching this issue

                Created:
                Updated: