allow a scorecard to count the number of tags in a field and incorporate that into the score
This is a spin-off to the ideas that request that "custom fields" be incorporate-able into a score. It would be great if it wasn't just hard-entered integers, but anything that could be counted.
For example, we use a tag field to indicate which o...
Oleg Yazvin
about 5 years ago
in Epic
2
Future consideration
Dynamically select assigned users on Workflow Board
I love the new Workflow board and actually like the Assigned To swim lanes (i.e. who the responsible PO is for each Master Feature), but having to manually assign users is a pain. The entire company is in one giant Aha workspace meaning thousands ...
Dan Eisenhut
over 5 years ago
in Epic
0
Future consideration
Allow conversion of Epic to Feature when the Epic contains features
When an Epic has no child features, you can convert it to a Feature. When an Epic has child features, today you cannot convert it to Feature. It would be a smoother workflow to allow Epics with child features to be converted to a Feature
Emily Yankush
about 1 year ago
in Epic
0
Future consideration
Ability to filter dependency types on the custom roadmap or add a colour to the icon for different dependency types
The addition of the releated section on custom roadmaps is useful. However, it would be useful to be able to control which dependencies are shown. For Example I have created a custom roadmap of features I want all of those features to be displayed...
Andrew Brooks
over 2 years ago
in Epic
0
Future consideration
We've started building out our roadmap in Aha! using the Epics functionality. One thing I have found tricky is locating Epics after I've created them, as I can only see them within the context of a Release or Parking Lot. After enabling the "List"...
Guest
over 3 years ago
in Epic
2
Unlikely to implement
Tie master feature release to latest release of any sub features
If I move a feature into a later release, and that feature is a member of a master feature, the master feature release should be equal to or later than the release date of that feature so that the master feature is always considered to release equ...
Guest
almost 4 years ago
in Epic
1
Future consideration
When viewing the list of features in the master features, we can see the feature name, with a link to open it, and its status. The status should be a dropdown to quickly change the status of each feature directly from the master feature.
Guest
over 5 years ago
in Epic
0
Future consideration
We use master features to define use cases that require work from multiple products. The features linked to the master feature come from those different products. However, we need the ability to put requirements on a master feature to be able to t...
Guest
almost 6 years ago
in Epic
0
Unlikely to implement
If you link an initiative to an epic, it would be nice the features linked to the epic are automatically linked to the initiative
Who would benefit? Product owners What impact would it make? Less manual work How should it work? Link epic to an initiative Pop up to link the features as well (cfr when you move an epic to another release) Without use of automation rule (no ente...
Cindy J
about 2 months ago
in Epic
0
Future consideration
Prevent users from inadvertently moving Features' workspace
Who would benefit? Our company's 750+ workspaces What impact would it make? If not resolved, this can cause damage, manual work to re-create Aha! <> Jira integrations, and work becoming out of sync between the two. How should it work? We oft...
Donald Hebert
4 months ago
in Epic
0
Future consideration