RELATED IDEAS
Apply "customise terminology" consistently - not just in some places
"Custom terminology" states "you can customize the terminology that is used in Aha! to match the language your team uses" but this isn't true. Customised terminology is NOT applied in many areas of Aha! including Capacity planning. We don't use the terms "Release" and "Feature" but they appear in numerous places despite changing the terminology in settings. This means we have to do mental translation whenever these inconsistencies are encountered, which is confusing and annoying for our users.
-
-
-
-
-
-
-
-
- +2
The screenshot shows the project capacity settings modal; custom terminology doesn't flow through here. We use custom terms for features and epics, so where Aha uses feature, we use epic, and vice versa. However, this does not flow through into this modal, so the radio button labels are very confusing.
I'd definitely like to see this addressed. Nomenclature is really important and if there are areas where it's not clear, it's going to drive a lot of confusion.
Thanks for sharing this feedback. I'm sorry to hear that there are a few areas where we have missed the terminology updates. You mentioned the capacity report -- do any other areas come to mind? I'd like to make sure we include them in the feature to resolve this concern.