• 3
    • 13
    • 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 Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.

      Richer reporting with

      • Standard and custom dashboards including drilldowns to reports (dashboards are viewed by company executives to gain visibility to project tracking and pipeline)
      • Custom reporting
      • Exportable reports (as PDF and / or Word)
      • Printable reports
      • The releases report should include links to the epic, project or task, this would make it easier to makes changes based on the report result. (The exported release report should include this information as well)

            [JSWSERVER-25216] Richer Reporting

            Dear all,

            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            Those who look for Excel reports on Portfolio data may want to try this integration. While those who has a use related to printing may want to try this other integration.

            Aron Gombas [Midori] added a comment - Those who look for Excel reports on Portfolio data may want to try this integration . While those who has a use related to printing may want to try this other integration .

            Nicole Downes added a comment - - edited
            1. I would also find a “Team Member Allocation by Time Period” report very helpful as detailed by Dave 4/May/17
            2. Include Epic name in the export of the Scope Report.
            3. Printable version of the Schedule view shown on the screen, especially when the view needs to be scrolled to see all the data.  This would complement the share feature, which is very good.
            4. The Release date entered in Jira and used for the Jira roadmap is not reported in Portfolio.  Can these field be included in the Scope report, or are you expecting that we add it manually as the Target end date?  

            Nicole Downes added a comment - - edited I would also find a “Team Member Allocation by Time Period” report very helpful as detailed by Dave 4/May/17 Include Epic name in the export of the Scope Report. Printable version of the Schedule view shown on the screen, especially when the view needs to be scrolled to see all the data.  This would complement the share feature, which is very good. The Release date entered in Jira and used for the Jira roadmap is not reported in Portfolio.  Can these field be included in the Scope report, or are you expecting that we add it manually as the Target end date?  

            Roi Fine (Inactive) added a comment - - edited

            Thank you all for the suggestions, keep them coming   We can see that many of you are interested in capacity related reports. Please comment here for additional types of reports that can help you mange your projects portfolio. 

            Thanks eli.mata2088558049 we will look at each ticket individually and provide feedback when we decide to prioritize the respective features in our roadmap. 

            The Portfolio for JIRA team

            Roi Fine (Inactive) added a comment - - edited Thank you all for the suggestions, keep them coming   We can see that many of you are interested in capacity related reports. Please comment here for additional types of reports that can help you mange your projects portfolio.  Thanks eli.mata2088558049 we will look at each ticket individually and provide feedback when we decide to prioritize the respective features in our roadmap.  The Portfolio for JIRA team

            Eli Mata added a comment - - edited

            To properly tackle reporting I think we first need to tackle some shortcomings in Portfolio.
            Below is a list of issues that IMO would make Portfolio a better tool. Some, if not most of these, are reporting issues.

            • Make Initiative burn-down and Initiative reports available on JIRA Portfolio. JPOCLOUD-1918 
            • Replicate Theme field from Portfolio to JIRA Issue. JPOCLOUD-525
            • Force new tickets for specified Issue Sources to go automatically into the Later release. JPOCLOUD-1730
            • Having the option for the user to re-order/re-arrange column in JIRA Portfolio. JPOCLOUD-497
            • Allow Portfolio to book issues into sprints if capacity is still available. JPOCLOUD-1867
            • Allow ability to Filter by Sprint name in Portfolio. JPOCLOUD-1508
            • Ability to order statuses within columns. JSWCLOUD-9675
            • Provide a feature to select an active Sprint from a board. JPOCLOUD-1510
            • A mechanism for Bulk Updates in Portfolio. JPOCLOUD-1870
            • Using Parent link field in issue source corrupts hierarchy. JPOCLOUD-1894
            • Being able to assign stories directly to Initiatives. Rather than Epic then Init.

            Eli Mata added a comment - - edited To properly tackle reporting I think we first need to tackle some shortcomings in Portfolio. Below is a list of issues that IMO would make Portfolio a better tool. Some, if not most of these, are reporting issues. Make Initiative burn-down and Initiative reports available on JIRA Portfolio. JPOCLOUD-1918   Replicate Theme field from Portfolio to JIRA Issue.  JPOCLOUD-525 Force new tickets for specified Issue Sources to go automatically into the Later release.  JPOCLOUD-1730 Having the option for the user to re-order/re-arrange column in JIRA Portfolio.  JPOCLOUD-497 Allow Portfolio to book issues into sprints if capacity is still available.  JPOCLOUD-1867 Allow ability to Filter by Sprint name in Portfolio.  JPOCLOUD-1508 Ability to order statuses within columns.  JSWCLOUD-9675 Provide a feature to select an active Sprint from a board.  JPOCLOUD-1510 A mechanism for Bulk Updates in Portfolio.  JPOCLOUD-1870 Using Parent link field in issue source corrupts hierarchy.  JPOCLOUD-1894 Being able to assign stories directly to Initiatives. Rather than Epic then Init.

            David Mahoney added a comment - - edited
            1. Still on trial, but the only existing report we find useful is the Scope report.
            2. The project managers would like to share Portfolio planning reports with upper management
            3. Mostly as Excel spreadsheets

            Our #1 request is the ability to export Team data.  A simple report with Team Name, Member, Allocation and Skills would be useful.

            We’d also like to see a “Team Member Allocation by Time Period” report which would be bounded by dates (ie Jan 1 to Jan 31) and shows:

            • the work item
            • the team member
            • the skills they possess (of which one will be a role)
            • based on the calculation of the plan, the number of hours it is expecting they spend on the work item.

             

            Thanks,

            Dave

            Avaya Canada Corp

            David Mahoney added a comment - - edited Still on trial, but the only existing report we find useful is the Scope report. The project managers would like to share Portfolio planning reports with upper management Mostly as Excel spreadsheets Our #1 request is the ability to export Team data.  A simple report with Team Name, Member, Allocation and Skills would be useful. We’d also like to see a “Team Member Allocation by Time Period” report which would be bounded by dates (ie Jan 1 to Jan 31) and shows: the work item the team member the skills they possess (of which one will be a role) based on the calculation of the plan, the number of hours it is expecting they spend on the work item.   Thanks, Dave Avaya Canada Corp

            Hey Portfolio Team,

            1.  The release report, Themes, Schedule and Capacity.

            2.  Mostly the reports view is used by the users of Portfolio (Product Owners, Scrum Masters, Project Managers, Programme Managers, Portfolio Managers).

            3.  Embed at the moment, but would love some sort of PDF option, which is nicely formatted.

            4.  Exception reports and information on teams (if you are splitting time for an individual over teams, it would be nice to see some sort of allocation of teams somewhere without having to go the managed shared teams and drill into each person.  Also a report to see upcoming periods of absence for people in teams whether for leave or otherwise.)

            5.  Additional filtering on the toolbar for components / labels and potentially custom fields, and a grouping by a specific custom field.

            Our clients are super excited to use Portfolio, and are constantly asking me when new features are coming out.  Thanks to the team for building a product which changes our clients lives.

            Thanks!!!

            Lisa Schaffer added a comment - Hey Portfolio Team, 1.  The release report, Themes, Schedule and Capacity. 2.  Mostly the reports view is used by the users of Portfolio (Product Owners, Scrum Masters, Project Managers, Programme Managers, Portfolio Managers). 3.  Embed at the moment, but would love some sort of PDF option, which is nicely formatted. 4.  Exception reports and information on teams (if you are splitting time for an individual over teams, it would be nice to see some sort of allocation of teams somewhere without having to go the managed shared teams and drill into each person.  Also a report to see upcoming periods of absence for people in teams whether for leave or otherwise.) 5.  Additional filtering on the toolbar for components / labels and potentially custom fields, and a grouping by a specific custom field. Our clients are super excited to use Portfolio, and are constantly asking me when new features are coming out.  Thanks to the team for building a product which changes our clients lives. Thanks!!!

            Hi guys, we are looking into improving Portfolio's reporting capabilities. We are interested in your thoughts about the following:

            1. Which reports do you share the most in Portfolio today?
            2. With who do you share Portfolio's reports?
            3. How do you share Portfolio's reports?(embed in Confluence, link, etc..)
            4. What kind of reports would you like us to add?

            Thanks for your feedback & support

            The Portfolio for JIRA team

            Roi Fine (Inactive) added a comment - Hi guys, we are looking into improving Portfolio's reporting capabilities. We are interested in your thoughts about the following: Which reports do you share the most in Portfolio today? With who do you share Portfolio's reports? How do you share Portfolio's reports?(embed in Confluence, link, etc..) What kind of reports would you like us to add? Thanks for your feedback & support The Portfolio for JIRA team

            Oh my I just tried to print a report to embed in another document.

            Not a fun experience...

            Be nice if the reports could at least give the information that is displayed on the other screens in portfolio.  or if I had an option to customise the report....

            Matthew James added a comment - Oh my I just tried to print a report to embed in another document. Not a fun experience... Be nice if the reports could at least give the information that is displayed on the other screens in portfolio.  or if I had an option to customise the report....

            Please make sure you don't forget about Portfolio when thinking about better reporting - please don't just do it for cire JIRA

            Michael Gibson added a comment - Please make sure you don't forget about Portfolio when thinking about better reporting - please don't just do it for cire JIRA

              Unassigned Unassigned
              0c3dcb73abe0 Edward Tomazic
              Votes:
              97 Vote for this issue
              Watchers:
              58 Start watching this issue

                Created:
                Updated: