RELATED IDEAS
Inherit Initiative workflows
What:
Make an initiative workflow set at a product line level inherited by its children products/product lines.
Why:
It's cumbersome and error-prone to require setting every product in a product line to use the same initiative workflow. It would be easier to set the workflow at the product line level, and have all child products/product lines inherit that as the default.
-
ADMIN RESPONSEApr 26, 2018
You can now create workflows at the account level and have them automatically applied when you add new products.
2
MERGED
3
MERGED
© 2024 Aha! Labs Inc.•All rights reserved
The default workflows don't help with this, I got about 150 active products and can't change the workflow easily for those who've been set up before already. And to make matters worse, those previously created workspaces are associated with an "Example initiative workflow" which I'm not allowed to edit as it doesn't show up in the list of workflows. I'm confused.
The feature in the response doesn't actually solve the problem. The user will still have to go into each workspace to manually adjust the workflow.
I strongly agree as well. I worry as new products get added by product owners this step could be mixed and then products in the same product line could end up with different statuses. Thanks!
Correction *New Product is added (not initiative)
I strongly agree with the "Why" that Max highlighted above. It is extremely tedious to apply a custom initiative workflow to portfolios with 20 or more products. Not to mention, adding the initiative flow each time a new initiative is added.