Ability to Bulk Edit Requirement fields

It would be very useful to bulk edit requirement fields including:

  • Requirement assignment
  • Requirement logged effort
  • Requirement status
  • Requirement original estimate
  • Requirement logged time
  • Guest
  • Dec 16 2014
  • Shipped
Release time frame 1 month
  • Oct 17, 2018

    Admin Response

    Make Bulk Changes to Your Product Roadmap Data

    Bulk editing is now available in nearly all list reports. This allows you to quickly update most of your records including goals, initiatives, and requirements.

    Learn how to use a list report to bulk edit your product data.

  • Attach files
  • Kristian Kauper commented
    February 17, 2015 04:32

     This should be true of features as well: Ability to bulk edit, e.g.,

    * Tag

    * Estimate

    * Status

     

    Or take bulk actions, like delete.

  • Admin
    Suzanne Vaughan commented
    February 17, 2015 16:10

    Hi Kristian,

    You may bulk edit features today on the Features List view. Simply filter to get the list of features you want, then select all or some of those features by checking the box to the left of them. This will bring up the Bulk Edit button. 

  • Harrison Lynch commented
    December 5, 2015 00:11

    Wanted to bump this. Because there isn't an Aha to JIRA status mapping, we've a whack of Features that are now released, but the Requirements (which are linked to sub-tasks) still show up in various open statuses. even though the sub-tasks are in "Done" status.

  • Cathy Sherwin commented
    May 6, 2016 15:57

    Would also like ability to modify Requirement Workflow - specifically, the ability to remove "Status" entirely from requirements.

  • Anon Anon commented
    January 17, 2017 14:24

    bulk edit custom fields at requirement level will also need to be deployed as well please.

  • Anon Anon commented
    January 17, 2017 15:05

    Bulk Edit of Custom Fields should be added to this idea as a need and not a desire please.

  • Ravi Rao commented
    May 24, 2017 16:40

    This is an absolute necessity, and additionally we need to have the ability to track the over requirement status based on individual status. For Eg. A feature could have 5 requirements, 3 of which are committed and completed for Release 1. The tool should have the ability to promote the feature along with the two incomplete requirements to the next release. The overall status of the feature should also reflect the combined status of the requirements.

    Coming to the ability to bulk import the feature  along with the requirements, what ever is available on the GUI to update for a feature or requirement should also be bulk importable, through a csv or Jira.  

  • Guest commented
    May 25, 2017 10:12

    This would be a valuable labour-saving error-reducing tool for us, especially since bulk-moves of stories done in JIRA do not get updated in Aha! (so bulk moving them in Aha! is one way to avoid this other problem).

  • Mark D commented
    June 7, 2017 23:03

    This should also allow for the bulk edit of the feature to which a requirement is assigned

  • Donald Hasson commented
    June 14, 2017 16:53

    Agree especially with Harrison Lynch. Bulk edit of req's is really important. But definitely think the req's status should inherit from the feature. If the feature is shipped (and assuming the req's have been moved out that the feature didn't actually get), the req's are obviously now considered shipped.

  • Mark D commented
    June 26, 2017 22:49

    This feature should also allow for bulk moving of requirements to a different feature

  • Brody Todd commented
    September 25, 2017 17:25

    This costs my team a lot of hassle. On average we deliver 30-40 requirements every couple weeks. When we ship a release, this means spending a tedious amount of time just clicking through requirement statuses.

  • Kelly Gold commented
    December 5, 2017 23:15

    Please.... We need to bulk delete a single requirement, or bulk add a single requirement to a set of features. 

  • Ralph Seibert commented
    February 9, 2018 18:28

    I am also in support of this idea because we have several different groups that we have or orchestrate with that has different requirements and it requires us to change custom fields at time to align with these changes.   The ability to bulk change our changes would really optimize our usage of the system.

  • derek commented
    May 21, 2018 18:37

    Is there an ETA on when this is "Likely to implement" Its been four years!

  • Lindsay Hanrahan commented
    August 27, 2018 15:38

    We really need this feature to be implemented! We use the "requirements" level very intensively and it is a huge source of inefficiency to make the same change to potentially hundreds of items so that things stay aligned.