There should be a way to count the number of total issues that were created within a Portfolio.
Currently only unresolved issues is available for this purpose, but we would like to be able to see how many total issues occured within each portfolio instead.
This is easily done with an issue report filtered by project portfolio. You can also add this to a dashboard and attach the dashboard to a portfolio and leave off the portfolio filter.
Former Community Member
4/9/18
Thank you Marty - That's what I was hoping to see but Portfolio Name does not seem to be an available field on an Issue report.
My workaround was to create a custom field at the project level with the calculation, "Portfolio.Name" and then referenced the calculated field on the Issue form, since the real portfolio name field was inaccessible.
Jim - When creating an issue report, you can filter on ISSUE>PROJECT PORTFOLIO ID and start to type in the name there. You can also filter directly on the project portfolio object further down in the list of objects. If you are trying to add it as a column in the issue report, there is a field in the issue object listed simply as PORTFOLIO. It displays the portfolio name and in the text mode shows up as linkedname=direct namekey=portfolio querysort=project:portfolio:name valuefield=project:portfolio:name valueformat=HTML viewalias=portfolio
Former Community Member
4/9/18
Marty - thanks for your reply. This is a great idea but allow me to be more specific with our scope for this report.
My end goal is to see how many total Issues were created in each portfolio, and compare that number against all other portfolios on a number of charts (Combined line graphs and Bar Charts).
A bit of background. We have a Portfolio for each Business Division and issues to track change requests. The Director of Operations would like to see the total number of Change Requests that each division submits each week, so we can better understand the needs of our various business divisions.
If Portfolio Name were available as an option in the report builder, this type of issue analysis could be done much more easily.
Got it. Simple. Matrix report. Group by Project Portfolio>Name and Issue Status (or Type or whatever you need).
Filter on Issue Type (or status or as needed).
You can then do a stacked bar, pie, or whatever you need.
When you say unresolved though, that brings up an interesting question. Are you converting these issues to projects or tasks? And if so, are you retaining the original issue? If not, the issue is no longer there for reporting. You'd need your SOP to be to retain the original issue and tie it as a resolving object.
