Our data model is such that every workspace in Aha! maps to a platform and we use a custom table to define the mapping. Since the field is mandatory for all objects in said workspace, we make the field mandatory when creating new features. We can'...
Allows much easier to iterate, more standard, and simpler to follow along version of diagrams/charts within documentation. GitHub and Notion have recently adopted the same library (mermaid) allowing for standardization across tooling.
Barnett Klane
over 2 years ago
in Development
0
Future consideration
Burn *Up* charts for Sprints, Releases, Epics, and Features
My company would find it useful to have Burn *Up* charts that show how the effort completed is tracking against the scope of a release / master feature / feature For more on the requirements for a Burn Up chart and why it is more useful than a Bur...
Mark D
over 7 years ago
in Releases / Sprints
2
Future consideration
Aha! Develop: Customize the "Engineering work" heading in Backlog Management
We use Aha! Develop for a variety of teams and use cases. These are not always engineering teams, so we'd like the flexibility to customize this heading.
Dale Potter
about 2 years ago
in Backlogs
1
Future consideration
TestRail is a popular test case management tool. I would like a TestRail extension for Aha! Develop that provides deep integration between Aha! and TestRail.
Jeff Tucker
almost 3 years ago
in Extensions
0
Future consideration
Develop team owners should be able to manage team members
Who would benefit? Team owners that do not have the customization admin role What impact would it make? Currently Develop team owners do not have a place in the team settings to manage the users in their team, but this is a permission owners have ...
I want more control over filtering cards on the workflow board. For example, I'd like to be able to filter all of the cards based on the value of a custom field I've added.
Mark D
over 3 years ago
in Workflow boards
2
Future consideration
Consolidated workspace for product and development
My team uses Aha! Roadmaps with Aha! Develop. We find that we often have one team per workspace – everything on the Product A roadmap goes to the Product A team. We find ourselves switching between the Roadmaps workspace and corresponding Dev...
Moving a feature from the workflow board to the prioritized backlog should automatically unassign it
Who would benefit? All product and develop teams What impact would it make? Ensure the prioritized backlog is tidy How should it work? Moving a feature from the workflow board to the prioritized backlog should automatically unassign it
Engineering managers & team leads sit "in between" Aha! Roadmaps and Aha! Develop. They more than just team owner permissions, but not full workspace contributor permissions. Key use cases Team leads can provide initial estimates on features b...