Share your product feedback

Add a new idea Subscribe
Status Future consideration
Categories Features
Created by Max Chanoch
Created on Feb 24, 2015

RELATED IDEAS

Adding Feature Workflows for Feature Types

Aha! allows you to create feature workflows for a product, but not for a feature type. It would be helpful to have product workflows applicable beyond the product - allowing users to customize completion workflows per feature type. 

Let's look at two obvious examples.

Enhancements: Under Consideration >> Ready for Development >> In Design >> In Development >> In QA >> Ready for Production >> Pushed to Production. <Will Not Implement>

Defects: Under Review >> Confirmed Defect >> Prioritized >> In Development >> In QA >> Ready for Production >> Pushed to Production. <Will Not Implement>. <Not A Defect>. 

  • Attach files
      Drop here to upload
    • Jamie Lefkovics
      Reply
      |       Dec 1, 2021

      I land at the ideas page too often - meaning I need something that is not there today and I end up here. We need custom workflows for features of different types that existing in different types of workspaces.

      Eg. Marketing owns features that exist within Product Releases. Marketing requires the ability to run their own status workflow just for their own feature set.

      Need yesterday of course. Its been since 2015... Future Consideration. Not holding my breath. :(


    • Guest
      Reply
      |       May 26, 2021

      Seeing the created date for this idea makes me loose hope though. ☹️

    • Guest
      Reply
      |       May 26, 2021

      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.

    • Guest
      Reply
      |       Jul 18, 2017
      I was wondering if it is possible to create a different status workflow for a specific Feature type?
       
      The reason I am asking is because we like using the 'research' feature type for the UX and user research my team do, but the elaborate statuses for development work don't make sense for this feature type.  If a feature type is 'research' we would like the status work flow to be simply - Under Consideration -> Doing -> Done.
    2 MERGED

    Multiple workflows per product

    Different types of deliverable will be treated in different ways, and so we need the flexibility to associate different types of feature with a different workflow
    Guest over 6 years ago in Features 0 Future consideration
    2 MERGED

    Custom Statuses for User Stories based upon the type of User Story selected

    My team and I are very interested in creating templates for various types of user stories is Aha Develop. The goal is for each individual user story template to have a unique set of status options based upon the type of user story, (i.e., feature,...
    Guest over 2 years ago in Ideas portal 0 Future consideration
    Idea management by Aha!
    Create your own ideas portal to crowdsource feedback
    © 2025 Aha! Labs Inc.•All rights reserved