How to generate stakeholder-friendly reports in Jira Portfolio?

I'd like to use JIRA portfolio to directly communicate the roadmap to various stakeholders. For that a few elements are missing, and I'd be happy to have them:

Changes to reporting views

  1. Ability to see the "compact" milestone/release view also as part of the reporting section and not just as split screen with the backlog. This view is very useful for business stakeholders.
  2. Show stream names directly on the screen w/o need to use tooltip (both for convenience and for the ability to take a screenshot)
  3. Release names can be long and run over each other, or even happen on the same date. Please use text wrapping and add also another line if needed. Same goes to initiative / epic names in the relevant views.
  4. Show dependencies on epics view.
  5. Add a view that shows Initiatives and epics together (Initiatives as buckets of epics).
  6. Ability to filter by initiative (Initiative = project, need to focus on one project and see only that).

Defining / using preset reports

  1. (Basic must have) Ability to generate a specific URL per view that can be saved as preset view and/or shared via email. Can't expect each stakeholder to re-create the report every time.
  2. (Advanced) Export a series of preset reports to ppt / google slides / pdf / confluence page which is could be updated by one click / live to generate all the preset reports.

Thanks

Ran

 

1 answer

I strongly agree with your deep link suggestion:

(Basic must have) Ability to generate a specific URL per view that can be saved as preset view and/or shared via email.

JIRA Portfolio is an amazing little tool, but there is no way to report the results either upward to stakeholders or downward to team members.  The whole point of this thing is to help me to bridge the gap between the VPs above me and my scrum and kanban teams, right?  So then how am I supposed to communicate the plans from JIRA Portfolio to those VPs above me? And how am I supposed to communicate the schedules that it generates to the teams who are supposed to do the work?

I love this tool, I'm just baffled by the enormous parts that are missing.  What's the point of a tool that generates output that you can't share with people?  Are my VPs and also the individual workers supposed to go into Portfolio and interact with the scheduling UI?  That's never going to work.

Suggest an answer

Log in or Join to answer
Community showcase
Josh Frank
Posted Dec 01, 2017 in Portfolio for Jira

Portfolio for Jira: Share your tips!

The Portfolio for Jira team wants to hear from you. Share your top tips for building a great Portfolio for Jira plan for a chance to win some Atlassian swag.  Do you structure your teams i...

542 views 6 8
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot