Skip to Main Content
Status Shipped
Categories Product
Created by Guest
Created on Mar 25, 2015

Enable the terms "release" and "feature" to be defined within a product

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.  

  • Attach files
  • Guest
    Reply
    |
    May 12, 2015

    I have this same issue.  Keeping nomenclature the same across tracking software would eliminate confusion.

  • Suzanne Vaughan
    Reply
    |
    May 8, 2015

    Hi Karthik,

     

    We agree. 

  • Guest
    Reply
    |
    May 7, 2015

    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.

5 MERGED

I would like to rename Aha! menu items to match my Jira objects: Initiative = Epic; Feature = Story; Requirement = Sub-Task

Merged
To help Engineers who use both Jira and Aha! to avoid confusion.
Guest over 9 years ago in Jira 2 Shipped
2 MERGED

Enable renaming of "Feature" field and "requirements" when integrating with JIRA

Merged
This would help to avoid denomination confusion when Product Managers and Dev. teams are separated.
Guest about 9 years ago in Jira 0 Shipped