Not just the fields present in your epic/release/feature/idea template. I have flows for each of these record types that add new fields for input later on and would like to run automations on them, but can't unless I add them to the template used ...
Danielle A
over 3 years ago
in Workflow boards
1
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
almost 8 years ago
in Releases / Sprints
2
Future consideration
We would like to be able to view an individual's work schedule when reviewing capacity planning at an individual level. Capacity currently defaults to 8 hour day and workschedule is only supported at team level.
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.
We like weekly product roadmapping digest from Aha. We are looking for ways to create weekly/bi-weekly reports that tracks additional metrics such as sprint/release velocity, point burndowns, etc. and how these metrics are trending over time from ...
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 ...
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
almost 3 years ago
in Sprints
2
Future consideration
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
almost 3 years ago
in Development
0
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...
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'...