Skip to Main Content

Share your product feedback

Status Already exists
Categories Features
Created by Guest
Created on Feb 22, 2018

Customize look/feel of Feature Details to allow most critical information be visible

We have customized our features with additional fields. We find that most of the time, our feature detail screens result in having a lot of white space with our custom fields scrolling down the right side. Our custom fields tend to have more valuable data that I would like to move to the primary screen under the description when viewing the detail.

I have attached an example of all of our white space and you can't see all of the fields on the right side, because you have to scroll to see them.

I'm getting a lot of feedback from our teams that don't like the look of Aha for using it for information because the information they need isn't readily available and they have to scroll to get to it and as a result, we are wasting valuable real-estate on the page.

It would be hugely helpful to be able to adjust the screen so that we can make better use of the real-estate on the page.

  • ADMIN RESPONSE
    Feb 22, 2018

    To make your custom fields appear below the feature description you can use the custom field layout screen to move fields to the "Bottom section".

  • Attach files
  • Brent Schumann
    Reply
    |
    Jan 29, 2021

    Hi, I can't seem to find how to do this in Aha, at this time. Was this feature removed? We really need the acceptance criteria as a custom notes field that we map to Azure DevOps Acceptance Criteria. IMPORTANT: We need that field to appear below the Description field so it has the same prominence and it can use the same real estate.

    Can you help me?

  • Guest
    Reply
    |
    Feb 22, 2018

    Thanks for this guidance! For what it's worth, I did not find this clearly documented. When I saw the "Bottom section" that description made me think it was at the bottom of that right section, since the "Top" refers to the top of that and Middle doesn't appear usable at all.

    You may want to update/clarify in your documentation.