for Portfolio Forecaster for Jira Cloud
Powered by Released
Allow a user to create group forecasts from precanned templates set up according to best practices.
Add widget to confluence page that allows you to pick a group forecast to show on the page.
Allow users to share forecasts to stakeholders via email. The email would be a one-time action containing the current forecast.
Jira Cloud - Advanced Edition (coming soon) Provide an option for automatically re-running the forecast on a custom schedule in addition to the existing manual option. Granular choices, including day of week, specific dates in a month, and/or time of day will be available.
Not started items with no remaining work can be forecasted based on designated configurations. Options are still to be determined but are likely to include options based on historical data and perhaps even t-shirt sizing.
Right now if you share a forecast portfolio with someone, they can see all contents there regardless of the permissions on a group forecast. We will be updating this to honor forecast permissions. When we do honor these permissions, If you are invited to a forecast portfolio and don't have permission to see one or more of the included group forecasts, you will see a note letting you know which forecasts are excluded due to your permissions so that you can discuss that with the necessary people.
Currently the new Portfolio Forecaster only supports Parent containers via Issues. We will be adding support for forecasting by version container as well.
Allow users to subscribe to get an email update when the forecast updates.
A standalone SaaS version of Portfolio Forecaster would be useful for those who are working in systems without an integrated solution. It would also work well for use in training situations if data can be uploaded.
Allow forecast admins to enter data into a field called executive status. Allow viewers to see the latest status for a forecast. This would require the status text to be stored in AWS so it can be displayed on the forecast. This will unlock the capability of future features such as displaying on any forecast portfolio the forecast is added to and even sending email updates. If this interests you, is there any value in having the previous statuses or just the latest?
Show indicators of trouble inside forecasted items (like blocked or past-due work)
If a forecasted item has a due date, allow the user to see the history of the likelihood of meeting the item's due date over time.
Allow the user to see the history of the forecasted date for a particular forecasted item over time.
This feature would allow users to see the latest executive status from each group forecast included in the forecast portfolio. This is dependent on the executive status feature being added to group forecasts.
The dashboard (aka home page) would have an area that shows items from your favorite forecasts that have at risk due dates. Potential configurations could be changing which forecasts are viewed and defining what %ile "at risk" means.
Provide users with a more visual display of a forecast via a Gantt chart based on their chosen confidence level/likelihood. The difficulty is finding the start date in the simulations so we may visualize a fuzzy start time if necessary.
Integrate Portfolio Forecaster into the cloud version of Azure DevOps
Allow the user to see the history of the number of unfinished child issues within a particular forecasted item over time.
Build a dashboard gadget that can display a group forecast on a Jira dashboard. Please comment with desired settings other than selecting the group forecast itself.
Build a dashboard gadget that can display a forecast portfolio on a Jira dashboard. Please comment with desired settings other than selecting the forecast portfolio itself.
When adding a URL for a group forecast to Confluence, support the various link formats that exist: URL, Text Link, Card, and full display
When adding a URL for a forecast portfolio to Confluence, support the various link formats that exist: URL, Text Link, Card, and full display
After a forecast is generated, allow users to hide individual items from the current view.
In addition to the current capability of choosing a relative date we need to allow users to choose more specific date ranges or even use latest but exclude certain sections of it (like christmas break). This will allow users to choose data that more accurately reflects the time being forecasted.
When group forecasts are configured into a portfolio, run a forecast on the portfolio as a whole to apply the impact of any cross-team dependencies.
When a user leaves Jira, allow admins to reassign the forecasts and portfolios they have created to another user or archive them.