RELATED IDEAS
Glossary of terms/business context
Definitions for terms/concepts between product lines often vary. It would be great to be able to create a glossary/ubiquitous language archive where definitions can be linked to product lines or different products. This will help developers use business language in code, and foster understanding between stakeholders in different departments.
Examples:
"administrator" in one product line may mean a sales partner versus "administrator" in another product line being someone in the marketing department.
"Username" in one product may have specific business rules versus "username" in another.
We use event storming / domain driven development so this would mean less static documents and more easy linking between ubiquitous language contexts.
-
ADMIN RESPONSEJul 22, 2022
Thank you for your idea. We would recommend creating a product note to store product or team-specific details such as these.
At this time, we are unlikely to implement this idea. We hope you can understand.
© 2025 Aha! Labs Inc.•All rights reserved
Hi Sean, thank you for the additional detail around your use case. Another potential solution here would be to leverage a custom table. You can link custom table records throughout Aha! and use them in reporting. For example, creating the alphabetical list you noted above. Custom tables are available for customers in the Enterprise+ plan. Thanks!
Glossary of market and product terms is a critical enabler for smooth communication. Product notes are not a user-friendly mechanism for providing such a glossary of terms but they seem to be the best tool Aha! currently offers. Better would be if I could create "Terms" and link to them anywhere in Aha!. Then I could define them once and access them easily via URLs or Search. I could alternatively go into the Glossary of Terms page/module and see an alphabetical list of these terms as well. Please reconsider as this is a very important feature in legacy requirements management tools offered in the market -- ie Rally, IBM CLM. Your current suggestion - to make as flexible - would require creating a separate Note page per Term. That is a terrible UX.