Now that I've started using Aha for the product plan, other areas of the organization are asking if they can use Aha for enterprise project planning. It looks like a "release" could be considered a "project" in their terms. And a "feature" could be considered a "task" under normal project planning tools. Enabling them to rename "features" and "releases" would help them understand how they could best use the tool.
I have this same issue. Keeping nomenclature the same across tracking software would eliminate confusion.
Hi Karthik,
We agree.
Note that the term mapping should be at each product level (granularity) rather than account level. In our large company we have multiple product lines, products and each of these groups have nuances in respective process.