Custom Fields at Requirement Level

Is it possible to create custom fields at the requirement level? For example, we want to set prioritization at the requirement level that will push into JIRA. We would want to create a custom field for this.

  • Guest
  • Oct 24 2014
  • Shipped
Release time frame 1 month
  • Dec 14, 2016

    Admin Response

    We just launched the ability to add custom fields on requirements. You can now add any custom field type on requirements to help better organize and communicate requirement details to your team. Check out our blog post for details.

    We know that many of you are also interested in the ability to sync custom fields to third party dev systems including Jira, TFS and Rally. This feature enhancement is currently planned and coming soon. Please subscribe to it here to track the latest updates.

  • Attach files
  • Connor Tobin commented
    8 Feb, 2017 11:02pm

    You made us really happy.

  • Admin
    Ron Yang commented
    14 Dec, 2016 06:45pm

    Kaitlyn - we just updated the link to the associated idea in the admin response. You can also access it here: https://big.ideas.aha.io/ideas/APP-I-3539 

  • Kaitlyn Moore commented
    14 Dec, 2016 06:18pm

    I cannot follow the link in this email, it’s telling me that I don’t have access. Was this the internal link to the idea?

  • Shri Iyer commented
    11 Dec, 2016 01:08am

    This idea is open from 2014 and it has been 2 years. Can Aha please add a custom field at the requirement level? Our requirements from aha map to user stories in JIRA and currently we have no way of syncing up between the requirement and the jira story

  • Fidel Zawde commented
    6 Dec, 2016 08:59pm

    Yes, we need this!!! This would allow us to create the specific estimates per device / platform and have it roll up correctly into the requirements and allow us to filter quicker by requirement.  

  • Brian Rogers commented
    6 Dec, 2016 04:13pm

    This would be a great help for our custom GitLab integration. We would like to link issues in GitLab to Requirements in Aha and would need to represent each issue's Status on the Requirement. Thanks!

  • Guest commented
    2 Dec, 2016 03:15pm

    Sorely needed

  • Connor Tobin commented
    1 Dec, 2016 03:35am

    Any Luck on getting this executed?

  • Kaitlyn Moore commented
    29 Nov, 2016 08:11pm

    Not only do we ABSOLUTELY need this, but we also need to make sure we can map it to our integrations to push when we push to development -- in our case to VSO.

  • David Vins commented
    13 Oct, 2016 02:58pm

    The second most popular idea, two years old, and still only marked as Likely To Implement?

  • Justin Curry commented
    11 Oct, 2016 10:10pm

    This is a big for us because we don't use sub-tasks in JIRA do to how messy they are to manage on the JIRA Agile Scrum board.  The developers use the Checkbox plug-in to manage their development tasks which is a lot easier than forcing a developer to try and create sub-tasks.  Therefore, our acceptance criteria for the story won't get mapped over into the Aha Requirement.  I'm talking importing from JIRA but still need a field in the Requirements for the acceptance criteria to push to JIRA.  Maybe you could add Acceptance Criteria as a Aha defined core field in Requirements and that would get me by...but, still would be nice to add custom fields in Requirements for other JIRA mappings to stories as well.

  • Oladayo Famakinwa commented
    10 Oct, 2016 04:16pm

    We want this idea too.  We need to add custom field for Acceptance Criteria and Component 

  • Shri Iyer commented
    28 Sep, 2016 07:53pm

    Apart from adding a custom filed at the requirement level, it would be cool to tag a requirement. We have the need to tag a requirement under a feature.

  • Andrew Ardron commented
    9 Sep, 2016 11:08am

    I really, REALLY REALLY NEED THIS, I want to put data at this level to integrate this with other systems we are using in house. THERE ARE LOTS OF VOTE ... CAN WE HAVE THIS ASAP? 

  • Guest commented
    26 Aug, 2016 05:32pm

    Definitely need this. This is one of the first things we noticed not supported when we looked at moving requirement data from another tool into Aha. We would like to define a "business justification" field (as well as other fields) at the requirement level but will do so at the feature level for now.

  • Guest commented
    20 Jul, 2016 11:53am

    Chalk up another vote here; really would like to see this and JIRA story labels synced up to Aha!

  • Mahima Gupta commented
    29 Jun, 2016 08:32pm

    It seems that "Feature" isn't a very good way to assemble several requirements in one category. I frequently have to address the priority of each "requirement" and this cannot be done by prioritizing a "Feature". As an example, a "feature" would be "Physical attributes" and "Requirements" could be "Footprint", "weight", etc. Each of these requirements could/ should be tradeable depending on engineering and market constraints. 

    Aha! team should really make sure that the basic product management needs are addressed first: MRD and Requirements definition. Aha! is a very helpful software, but not necessarily great at solving some of the critical and basic user challenges.

  • Patsy Jones commented
    2 Jun, 2016 03:32pm

    This would be fantastic, we would love to be able to add a custom field at requirements level, this would mean that I would be able to add acceptance criteria to my requires and map this filed to the acceptance criteria filed in visual studios

  • Jordan Glasgow commented
    2 May, 2016 08:16pm

    +1 - I would like to see ability to add story points & acceptance criteria at the story level. We'd like to do this in Aha prior to syncing with Jira. 

  • Guest commented
    26 Apr, 2016 02:46pm

    Hi, we have mapped a custom Aha Epic (Feature) field to Acceptance Criteria in Jira Epics but can't do the same for Stories (Requirements) which I would argue is way more important.

    Also, this is the second most voted unimplemented idea. I know that's not the only criteria for prioritizing feature requests but customers have been asking for a while...

  • Load older comments
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • and 57 more