The progress % on a feature should be in sync with the status of the feature. When the status changes so should the progress %. Using to-dos, requirements, or estimates to drive the feature progress % isn't an option for us as different groups may or may not use those functions. Instead we would like to drive the progress bar based on assigned values related to the features status, for example:
|Feature Status||Progress %|
|Ready for Development||40%|
|Ready to ship||90%|
As we are trying to standardize reporting methods, and most of our Product Managers missed updating the progress because is manual. I see a great advantage to having this option directly from Aha! of customizing an automatic rule based on different status
In design = 25%
In development = 75%
Will Not Implement = 0%
I hope you can consider this request in your future releases.
I am in full agreement that we need this capability. Right now we have to update manually, which the Product Mangers don't want to do -- I particularly agree with this means as an option of updating the progress - where we can define our status and the progress % -- do not not something that is pre-defined -- I need to define myself.
Ready for Development
Ready to ship
I see. Thank you for the additional context! That is helpful and I can definitely see value in a more detailed progress bar. It will be great to see what others think as well!
Thanks @Austin - love the direct engagement!
All great features you've linked to.
Apologies - I copied my comment from a helpdesk ticket where there was more context!
I was referring specifically to the 'Features Board' where you set a progress bar linked to completion of underlying tickets in JIRA (attached)
It's currently just say 50% green if 1 ticket is open and 1 ticket is closed. Would be great if you could map statuses to a couple of colours to show progress with a bit more nuance
Hi Jon, are you referring to the status workflow on a feature? If so, I did want to point out that you can fully customize the status options and associated colors. This article explains in more detail. You can then setup status mappings in the Jira integration as needed using the customized workflow. I hope that helps!
I'd also like to see more options around progress - although I'd see it drawing from underlying tickets/via integration - but with increased gradation - e.g.
Currently – it seems to default to ‘Green = Closed’ – all other statuses clear/light grey.
i.e. as part of the JIRA integration – I could set a status mapping for 3 rather than 2 colours – e.g.
Green = Closed
Amber/dark grey = in progress (and related statuses) or say in testing (and related statuses)
Clear/light grey = not started (and related statuses)
Need this asap. Very important to automate this and set the progress as complete when the feature is marked as complete.
All I need is a simple setting.... as opposed to the multiples.
IF Feature status is changed to Shipped, then automatically update progress to 100%
IF Activity status is changed to Completed, then automatically update progress to 100%
This is really a basic requirement and surprised its not there already. We have dozens of features and activities that have misaligned status and progress reporting. We cannot make users own this problem - need the above ASAP!
I agree, this is really important for our team.
Sometimes our features do not have any requirements against them and because the only option is to have it as 'Calculate from requirements completed' it marks the feature as 0% complete even when it marks as done!
It is a real pain and is causing big problems with our roadmapping % complete.
As a development team, our features have 11 steps (from backlog to completed).
It would be AMAZING to let stakeholders see progress based on a percentage of the current status. For my team, all statuses are weighted equally so it would be 1/11, 2/11 and so on, rounded to a percent.
I would love to feature these in my pivot reports and other reporting to show actual current progress on features. Thanks!
Frankly I would expect that to be automatic by default.