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
  • Dave Frame commented
    October 30, 2014 22:36

    We love this idea and need it!!!!  Specifically, we really want to be able to define an Aha! Score factor, Status Type, and Conditions of Acceptance at a requirement level.  And we cannot aggregate requirements up to features, given the nature of our product.  Custom fields at the requirement level would solve this problem.

  • Andy Darrant commented
    November 07, 2014 09:03

    Yep - me too - Custom Fields at Requirement Level would mean it would be easier to run and generate reports for notebooks. 

  • Richard Harrison commented
    January 16, 2015 11:55

    We really need this too!

  • Emilie Takeda commented
    April 09, 2015 09:09

    Hi Aha! guys, when are you planning to ship this? I'd love to have this too!

  • Guest commented
    April 14, 2015 17:01

    Definitely need this!  My scenario is having a Feature where the Requirements span multiple dev teams.  I need to be able to set a Team field at the Requirement level so that the stories in Jira show up in the correct team boards.  

  • Guest commented
    April 23, 2015 23:10

    I need this specifically so that I can have a custom field Team at the Requirement level such that the corresponding Jira story shows up on the correct team's board.  Often an Epic has stories that are worked on by different teams.

  • Jamie Burr commented
    June 04, 2015 20:50

    Any custom fields should be mappable to the TFS integration - ie, I would want the value in a custom field to carry over to a mapped field in TFS.

  • Mia Rucevic commented
    June 15, 2015 15:15

    We need it too! @Aha! any updates on this?

  • Leonard Schwartz commented
    July 15, 2015 22:00

    This would really aid me in some release note reporting

  • Emilie Takeda commented
    July 22, 2015 07:26

    Hi Aha team, any updates? We would need to interface some custom fields between Aha and Jira at requirement level and we currently can't because there are no custom fields at requirement level in Aha. There are 29 votes already! :)

  • Brian Dreyer commented
    August 03, 2015 20:44

    This would solve many reporting and team tracking needs that JIRA is very weak on.   Please add this feature!

  • Jonathon Leeke commented
    August 05, 2015 18:47

    This is necessary for products integrating with TFS.  Mapping requirements to User Stories or Backlog Items that may ship in different releases means we need a way to track the date that Story (Requirement) shipped, which we could store in a custom field on the requirement.  Features don't necessarily all ship at once for products with short release cycles, so we need more information on Requirements to help track them through the process.

  • Florian Leray commented
    August 11, 2015 08:32

    The lack of customization makes progress and priority management a real pain. So annoying not to have custom fields there that we are actually thinking about seriously decreasing the number of people using Aha. 

  • Emilie Takeda commented
    August 11, 2015 14:45

    Hi again Aha team!

    Could you communicate on a potential release date for providing this  great feature that a lot of people is expecting?? We seriously needed this feature since the beginning of our use of Aha and now that we are integrated with JIRA, not having custom fiels at requirement level makes it EVEN MORE PAINFUL!! :(

    We face an important resistance from some employees to use Aha because we cannot ease the migration from our existing tool which allows those custom fields... so we are basically loosing data from our legacy system! This is a big problem for change management!

    Please provide some visibility on the release date of this great feature! Thanks!

  • Martijn Schreuder commented
    November 15, 2015 16:05

    +1 for this.

  • Nicolas Quesne commented
    November 18, 2015 13:46

    Need it

  • Emilie Takeda commented
    December 01, 2015 15:59

    Hi Aha team,

    Any visibility to when the feature would be delivered? This is very critical for us now and we are thinking of dropping Aha because we feel that JIRA answers better to our need... that's very unfortunate but we may have to take this decision soon if this feature is not implemented... :(

  • Brian Dreyer commented
    December 04, 2015 18:23

    Would love this as well as we treat requirements as JIRA stories.  This would help us sync our more granular work estimates rather than the one sum total estimate amount.

  • Ed Wood commented
    December 30, 2015 15:36

    This is pretty important. Once you've gone to the trouble of setting up custom fields to import a bunch of features you would really like to experimentally demote some to requirements without it being destructive....
    I.e. you would like to be able to push and pull - all the while retaining your valuable imported meta-data...

  • Emel Meteoglu commented
    February 16, 2016 17:38

    I need this for a long time. I was hoping by now it was developed. An epic/feature composed of different stories which looks at our platform holistically. However different teams work on different requirements in the same epic. We cannot break the epic because it ruins telling the entire story. Moreover, some requirements are customer specific and customer focused solution teams want to see what requirements they should ensure that delivered. Need this ASAP! Please help us to solve this problem.

  • Guest commented
    February 25, 2016 08:26

    This would be really really useful for categorising requirements.

  • mohan kannappan commented
    March 10, 2016 01:08

     Too bad it is not there already..need it badly

  • Greg Hall commented
    March 21, 2016 14:48

    This would be extremely helpful at a requirement level to track LOE and estimated development hours to complete a Task. Would be also extremely helpful if this would push down to VSTS

  • Guest commented
    April 26, 2016 14:46

    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...

  • Jordan Glasgow commented
    May 02, 2016 20:16

    +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. 

  • Patsy Jones commented
    June 02, 2016 15:32

    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

  • Mahima Gupta commented
    June 29, 2016 20:32

    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.

  • Guest commented
    July 20, 2016 11:53

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

  • Guest commented
    August 26, 2016 17:32

    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.

  • Andrew Ardron commented
    September 09, 2016 11:08

    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? 

  • Shri Iyer commented
    September 28, 2016 19:53

    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.

  • Oladayo Famakinwa commented
    October 10, 2016 16:16

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

  • Justin Curry commented
    October 11, 2016 22:10

    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.

  • David Vins commented
    October 13, 2016 14:58

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

  • Kaitlyn Moore commented
    November 29, 2016 20:11

    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.

  • Connor Tobin commented
    December 01, 2016 03:35

    Any Luck on getting this executed?

  • Guest commented
    December 02, 2016 15:15

    Sorely needed

  • Brian Rogers commented
    December 06, 2016 16:13

    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!

  • Fidel Zawde commented
    December 06, 2016 20:59

    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.  

  • Shri Iyer commented
    December 11, 2016 01:08

    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

  • Kaitlyn Moore commented
    December 14, 2016 18:18

    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?

  • Admin
    Ron Yang commented
    December 14, 2016 18:45

    Kaitlyn - we just updated the link to the associated idea in the admin response. You can also access it here: 

  • Connor Tobin commented
    February 08, 2017 23:02

    You made us really happy.