On the feature board, in the small card size view, adding feature type icons would make it a much better view for getting an idea of what's going on in a release. Would be a nice alternative to text description of feature for the large card size v...
Suzanne Vaughan
almost 10 years ago
in Backlogs
0
Future consideration
What is the challenge? When running an effective Kanban system it's important to know where the bottlenecks in the process are. What is the impact? Currently I have to export the data to a spreadsheet to work out the problem stages. Describe your ...
Paid seat groups are useful for managing the assignment of seats to Roadmaps users. It would be great if this could be extended to support the assignment of Develop seats as well.
It is possible to re-open a shipped release to make changes that should have been included. The same logic should apply to sprints as there are various reasons I may need to make changes.
Dale Potter
over 2 years ago
in Sprints
2
Future consideration
Consistency between Roadmaps and Develop for record workflow
For the following Record Types (Epic, Feature, Requirement) In roadmap we can set each record type with its own workflow. However in Develop you can only pick one workflow for all three record types. We would like to have a consistent process of h...
Allow automation of related ideas from Develop team
We use an ideas portal to collect internal requests for our development team. I would like to automatically update the status of the idea as the related feature moves across the Develop workflow board.
Jeff Tucker
about 2 years ago
in Development / Ideas
1
Planning to implement
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
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'...
Aha! Develop: Split an individual's work schedule between 2 teams for capacity planning
My goal is to split a person's time between 2 teams (50/50). I'd like to have a schedule per team, so that I can indicate the days (or % of their time) they'll work on each team. Currently there is one schedule per individual, which is shared by a...
I really like the ideas overview page, however for collaboration and triage, it would be useful for us to be able to view the ideas in the workflow (kanban) view.
Nerissa Muijs
over 2 years ago
in Workflow boards
2
Future consideration