Defining a vision, a set of goals and initiatives are important, but one thing that is missing is use cases. Some PMs don't define them because they can be a bit redundant or simply unnecessary, depending on the product and target market, but some companies and products absolutely do. Many large software companies have sales forces that hone in on use cases as part of their sales process.
It would be very nice to, like goals or initiatives, be able to create and define use cases and then be able to relate them to features and releases.
Thank you for your idea. This is a great use for custom tables. This would allow you to define the key details that are needed to track use cases for your organization. You could then link them to features and other records throughout Aha! Alternatively, a simple approach would be to use a custom field to associate key use cases to features and other records.
This article provides more details on how to link key business details, such as use cases, to features.
Given the options above and other priorities, we are unlikely to implement this idea at this time. We hope you can understand.