RELATED IDEAS
This idea has been merged into another idea. To comment or vote on this idea, please visit A-I-16674 Fully support progress field in automations.
Automation rule to set a manually calculated progress field = 100% when status category is set to done
Merged
I like the agile rule of done or not done with an between status of in progress. So when I indicate the record is done and the progress field is manually calculated, it would be efficient to set progress field 100% complete.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +3
5
MERGED
4
MERGED
Allow automation rule to increase progress %
Today, progress on features can only be auto calculated based off when requirements reach a complete/done status. We would like the ability to show incremental progress. A simple way of doing this would be to allow setting the feature progress to ...
0
Future consideration
There should be a way to simplify the administration part of usage Aha! Completed means 100%, 100% means completed - it should be no need to change status + adjust progress bar. Those two fields are very much align and I can understand that someone like current setup but for the rest of the people - it should be possible to automate this part.
I received many feedbacks from the users asking to do something about it.
thanks!
In my case I use the integration with Jira. When a story is completed in Jira, I am able to set the correct status in AHA, but I have no way to set the progress automatically. In addition, not sure if it is just because I am not able to use AHA correctly, but the default for the Progress field is the manual update.
It will be really great to be able to use automations in cases like this.
If there is any hesitation around forcing the 100% when it's not really a 100%, you could solve for it with a prompt. For example, when the status category is changed to done a prompt could ask "Would you also also like to change progress to 100%? Yes, No, Other - enter a %___
This would really be a huge help for a user to maintain a consistent story and good data hygiene. Often times we forget all the little pieces that need to be changed so it would serve as a reminder and a time saver!