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...
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
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
Aha Develop: Show Prioritized Backlog changes in history
We use the Prioritized Backlog as part of our workflow in Aha Develop, records going from parking lots ("Engineering Work") or Roadmaps ("Product Work") into the Prioritized Backlog as they are refined and become ready.It would be really helpful i...
Jeff Tucker
over 1 year ago
in Backlogs / Features
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'...
Support automations that trigger only for active sprints
We have automation set up to notify by email when a feature gets added to a sprint. Is there a way to refine this to “added to a sprint in progress”? When we close out a sprint, and we have items that roll to the next sprint we get emails for each...
Jennifer Lange
about 1 year ago
in Development
0
Future consideration
Maintain cycle time data when team workflow is changed
Currently if I select a new workflow for my team and map my statuses to new statuses, I lose all past cycle time data because cycle time only focuses on the current workflow being used. Instead, I would like to see historical data that coincides w...
Max Robbins
over 1 year ago
in Development / Reports
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
In Develop, allow items imported from dev tools to be added to Product work
Who would benefit? Users who receive product requests via GitHub or similar What impact would it make? It would allow to add both Product- and Engineering-related items from importer extensions How should it work? When dragging an item from the im...
Alexey Zimarev
9 months ago
in Extensions
0
Future consideration
What is the challenge? We cannot associate a Release with a Team What is the impact? We cannot do necessary analysis in assigned Releases, commitment and deadline scores etc - stuff outside of Capacity. Describe your idea Allow the core Teams fiel...