RELATED IDEAS
Allow multiple workflows in a product
Within a given product there can be different types of initiatives and features. Aha! supports the concept of feature types and allows templating of the description field by type.
Would like to see an expansion of this concept to support configuration of different workflows by record type.
Example: A single product could have R&D efforts as well as product enhancement efforts that have a very different process, but apply to the same product. Currently, they have to adhere to a single workflow. Typically an R&D effort will have distinct gates it must go through, whereas product enhancements have a standard product development flow.
In order to allow for tracking of their statuses separately, currently there must be a different R&D product, eliminating the ability to prioritize the R&D work against the product enhancement work as well.
Would like to be able to assign different workflows to different work types within the same product.
© 2024 Aha! Labs Inc.•All rights reserved
We need having multiple workflows to allow UX design work on the feature, which is different than the PM workflow. Not having this results with 3 alternatives:
UX designers work only in Dev tool and not in Aha
UX designers work in a separate workspace than PM, which is a duplication of sub of the backlog (for features require UX work)
We set a very long and complex workflow that combines both PM and UX design statuses
I would like to have a workflow for Discovery/Research that is different from a feature/roadmap item that is going to be prototyped or sent to delivery. PM discovery does not need to be reflected in Jira for us (in most cases) and has a totally different process workflow than something that will go through a customer release.
A new experience has a completely different workflow than a datacenter deployment than a compliance item… yet they all belong to the same product, thus workspace. The concept of feature types is already there, but they only have an effect on the feature's description field, nothing else.
As we have thoroughly drafted a workflow for new experiences, all the others in the product team who don't work on new experiences, need to suffer from an unnecessary long workflow, asking for approvals from actually uninvolved parties, etc.
It would be a much needed, consequent, progressive enhancement to allow for multiple workflows in one product workspace, based on the feature types.
I am voting for this. We track different types of content activities on Aha! Different types of content will require different workflow steps.
We were advised about a workaround, but the end goal is to have all content in one area to make it easier to identify the status of content pieces, and limiting switching between workspaces (especially for executive staff).