Skip to Main Content
Status Shipped
Categories Account settings
Created by Guest
Created on Sep 7, 2017
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-5098 Add and remove standard fields in a custom field layout.

Ability to hide or re-label standard fields Merged

This allows our company to use the solution in our release planning language and greatly simplify the UX for fields we never will use

  • Guest
    Reply
    |
    May 22, 2020

    We are adopting Aha! functionality incrementally over time, and it would be a huge help in our adoption to be able to hide the fields we are not (yet) using so that we get users focused on the data that we are looking to use and not 'distracted' or initimidated by thinking they need to add data that we are not (yet) leveraging.

  • Danielle Machado
    Reply
    |
    Jan 9, 2020

    This would be great - some of the functionality associated with standard fields does not fit for out needs, so having the extra fields viewable in our Ideas or Features creates some confusion. The ability to at least hide them from the view would be preferable.

  • Jiyaad Naeem
    Reply
    |
    Oct 9, 2019

    Please do this

  • Roger Oliver
    Reply
    |
    Oct 4, 2019

    Agreed.  This would be very useful.  And would need to be configurable at the Product level, no only at the Account level.  We utilize certain record types and and fields uniquely for some of our Products / Product Lines and would like to make it more clear how the fields are to be used /populated.  For example, we have a Product Line for PMO Special Projects.  Under these Products, it would be nice to change the label of "Release Date (internal)" to something like "Planned Completion Date" and "(external)" to something like "Actual Completion Date".

  • Prerna Kanwar
    Reply
    |
    Jun 5, 2019

    This would be very useful for us and to ensure most important fields for our process (custom fields) are filled in and are always seeing at the top.

    Currently, these empty fields are sitting on the top and in the presentations I've to scroll all the way down which looses focus of attendees. Also, the impact is on Notebooks Im sharing with stakeholders and they don't realise they need to scroll it down.

  • Guest
    Reply
    |
    Aug 16, 2018

    This would be incredibly helpful as we establish processes & best practices of using Aha internally.

    Really, we just need to remove or MOVE standard fields in cards, so I can make sure the critical fields we need our PMs to regularly fill out are always "above the fold", and obvious to them.

13 MERGED

Change Aha! Status field names to "Workflow State"....or "Workflow Status"

Merged
With the new colored custom fields, we plan to report out on other statuses, and it would be nice to clarify that the "Aha! status" for Features, Master Features, Requirements and Releases, are really "Workflow" states/statuses. In our world, when...
Guest about 6 years ago in Features 0 Shipped
12 MERGED

Change Labels and Description of out of box fields

Merged
This is needed to be sure that our own requirements, terminology, and nomenclature can be implemented in the application and portal to ensure we are having a consistent user experience as well as ensure our requirements for data capture are not am...
Deanne Branham almost 5 years ago in Account settings 0 Shipped