It would be very useful to bulk edit requirement fields including:
This should be true of features as well: Ability to bulk edit, e.g.,
Or take bulk actions, like delete.
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.
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.
Would also like ability to modify Requirement Workflow - specifically, the ability to remove "Status" entirely from requirements.
bulk edit custom fields at requirement level will also need to be deployed as well please.
Bulk Edit of Custom Fields should be added to this idea as a need and not a desire please.
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.
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).
This should also allow for the bulk edit of the feature to which a requirement is assigned
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.
This feature should also allow for bulk moving of requirements to a different feature
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.
Please.... We need to bulk delete a single requirement, or bulk add a single requirement to a set of features.
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.
Is there an ETA on when this is "Likely to implement" Its been four years!
You won't be notified about changes to this idea.