Skip to Main Content

Share your product feedback

Customize navigation terminology separate from object terminology

We love the ability to customize object terminology in AHA. However, the navigation menu language follows this customization too closely, and we would love the ability to customize the navigation terminology separate and in parallel to the object terminology

E.g. Our team wants to use Epics as Epics and Features as Tasks. The majority of the work revolves around Epics. However, when we customize the AHA term "Feature" to our term "Task", the feature board now turns into the Task board, which confuses our users. We would like Epics and Tasks, but would like the Menu to say "Epic | Task".

There are several other ideas that ask for customization of the Navigation language, so it seems an easy enough UI to be able to declare custom object terminology in parallel to custom Nav terminology.

  • Attach files
      Drop here to upload
    • Jeff Shaffer
      Reply
      |
      Aug 8, 2022

      I'd add that it would be good to have the option to change 'List' in the Features and Idea navigation to 'View' (or the like), so that it doesn't confuse with the "List" menu under Roadmaps.

    1 MERGED

    Allow custom names for navigation

    Who would benefit? Accounts that have highly customized terminology What impact would it make? Allow account admins to clarify where artifacts are found in Aha with clearer tab names than what is automatically inherited from current terminology. H...
    Tim Haspert about 1 year ago in Account settings 0 Future consideration