Stop auto-reformatting text for Customized Terminology

When using custom terminology per product, Aha! automatically reformats text, capitalizing/not capitalizing and adding an "s".  The customized terminology would be much more beneficial were it truly customizable.  

  • Kelly Killeen
  • Jun 9 2015
  • Will not implement
Release time frame
  • Attach files
  • Admin
    Suzanne Vaughan commented
    June 09, 2015 20:12

    Hi Kelly,

    There is a format we adhere to which is to capitalize the first word of menu and object labels. In addition, if it should be pluralized such as a menu label, we do add an "s". Could you let us know specifically where you see the change and believe it should not be made? Thanks.


  • Kelly Killeen commented
    June 09, 2015 22:17

    For example, when changing the terminology of "release," I customized it to "Dashlet" and it pluralized it and renamed it "Dashlets."

    Also, when changing the terminology of "feature" to "User Stories," it removed the upper case "S" in "Stories" and renamed it "User stories" with a lower case S.

    The help text does indicate it will do so (pasted below), but I'm not sure why.

    The default text below is used in the navigation and throughout the application. Enter your own text for this product line or product. Use lower case, singular words as they will automatically be capitalized and made plural based on the context.


    Thanks so much!

  • Admin
    Suzanne Vaughan commented
    June 09, 2015 22:27

    Hi Kelly,

    Thanks for clarifying. The reason for this is so that there is uniformity in the menu options. The look and feel of the UI represents Aha! and it's important that the menu options are consistent. I hope that makes sense. 

  • Kenneth MacArthur commented
    August 18, 2015 22:38

    Hi Suzanne,

    One case we have where we wish you didn't change the capitalisation is where we rename release, feature and requirement to terms involving the acronym "QBO". This looks *really* ridiculous when made into a lower-case term.

    There are also places in the UI where an adjustment to the capitalisation is *not* made - this is arguably even worse, as there is then not even a consistent experience of the terminology across the UI.

    Would you agree that lower-casing inherently upper-case acronyms is Not A Good Thing?

  • Kenneth MacArthur commented
    August 18, 2015 22:38

    As a aside, you don’t customise the term “release date” – even though this is clearly a derivative term of “release”. Could you either provide a specific customisation for this term, or just use something more generic – eg, “XXX completion date”?