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
Defining / using preset reports
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Recently, as part of a series of Portfolio for Jira case studies, we spoke with Carl DiClementi, Director of Product Management at Factom about how he uses Portfolio for Jira. In...
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!
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