Unique field layout based on feature type

As others have said, for different kinds of work that the team use Aha for, it would be ideal to be able to have different layouts (and custom fields) depending on type (eg a New Feature type might need different fields than a Bug Type).

It seems strange that the use case of having different fields by Status exists (a much more niche use case to me) - this absolutely basic functionality of different layouts by Feature Type does not.

This would be very useful for a scenario I'm investigating related to a Feature Workflow.

Go To Market work can be relatively small in size and scope compared to Features, so are not currently captured on the feature workflow. But... they are really valuable, because they unlock Feature value by getting them onto the screens of different customers, and getting their feedback.

I would love to make that Go To Market work more visible on our Features workflow to facilitate planning conversations. The custom layout for a GTM work item could be much more lightweight than our Feature layout.

Also, as an Aha administrator, when I see the text 'Feature and requirement templates can be created per type.' in the workflow config screen, it does imply to me that this 'unique field layout based on feature type' feature is already possible. At least, that's how I read it : )

One of our use cases: we’re still trying to figure out how to use epics as milestones, and I’d like to have a layout based on what the PM chooses in the create step. So, they would click add epic, then choose the epic type (milestone/product) and based on that choice they would have specific fields visible on the record.

I see that this idea is now 6 years old. What is the likelihood that it will even be implemented, even with the amount of votes it has?

This is especially important when managing an integration with Jira, as bugs and features (tasks and user stories too) often have different field required fields. So in the current implementation, I have to add a ton of custom fields to a feature, even if they are not required for that feature's type.

It would be great to have multiple project templates in a single workspace that I could choose from for each "activity". We have multiple types of recurring projects that span mutliple workspaces that have different flows. Adding all possible fields isn't an option for maintaining efficiency.

We're currently using ClickUp in conjunction with Aha and plan on abandoning Aha if this kind of integration doesn't come soon.

This conditional logic should also be applied to initiatives and other record types. It would give you the ability to clean up the fields a user needs to see depending on what they are accomplishing with that initiative. Having to show all fields even though a user only needs 3 is a poor user experience and leads to bad data. 

Please find below 2 use cases to support this enhancement:

USE CASE 1:

My product has 2 feature types: Functional and Non-functional features.

My Functional Features need to have fields on them specific to them, for example, my functional feature needs to show a custom field called “Owner”. This field is used to show the Product Owner driving that feature.

My non-functional feature needs a field called “Architect”. That is the Software Architect responsible for the non-functional feature.

Yes, I could use a generic field that serves both, but this is just one example. My non-functional features will have very different fields than my functional features.

Additionally, the two feature types would have a different workflow. For Example:

Non-functional features will go from “not started”, to “Started” to “code Review” to “complete”

Functional features will go from “not started” to “in design” to “in development” to “complete”

USE CASE 2:

Another example is whether or not the item has User Acceptance Testing and Who that person is. Non-functional requirements will not need UAT or and Assigned Person, I wouldn’t want those fields on those types of requirements if only for the fact that they are just noise.

While we use Jira to track execution, it serves as a good example.. in Jira, I can create several different types of issues, and those issues have different fields. We have Defect issues and they have certain fields, we have User Story issues that have their own fields, Epics have their own, etc.

In Aha!, we also have different type of features that are unique in nature, contribute to the same project and product, but have their unique fields because they are in fact, unique.

No disrespect ;-) but I'd like to remove the Aha score and Tags field from our feature windows. Is there a way to do this?  We may eventually use Scores but right now it's just confusing folks. Thanks.