Allow extension settings to be configured at the team level
What is the challenge?
Extension settings can only be configured at the user level. Developers working across multiple teams must manually switch settings when moving between team contexts. For example, with the Claude extension, a developer on ...
What is the challenge?
Delivery risk settings are common to all record types; but I want to have different conditions trigger delivery risks for different record types. For example, if I want to trigger a delivery risk when there is no sprint as...
Enable users to view their assigned work across multiple Aha! Develop teams in one consolidated view
What is the challenge?
Users who are members of multiple Aha! Develop teams (e.g., a DevOps engineer working in both "Dev" and "DevOps" teams) cannot easily view all their assigned work from both teams in a single location. My Board currently on...
Keep date range calculation setting when removing a record from a sprint
What is the challenge?
When you remove a record from a sprint, it clears the date range which is good, but it also changes the calculation setting to Manual
What is the impact?
If you want all of your records to calculate off of Sprints, y...
Support Aha! acting as an MCP server for other AI agents line ChatGPT, Claude, Copilot or any other agentic framework. Users should be able to use Oauth to authenticate from an agent to Aha!. The MCP server should expose tools like the tools withi...
Bulk update "Location" for Features and Requirements
What is the challenge?
Currently, when features or requirements move between different stages (e.g., from Backlog Management to Prioritized Backlog), the "Location" field must be updated manually for each individual item. This is time-consuming ...
Ability to see requirements assigned to Team from Roadmaps on Team timeline
What is the challenge?
Teams are usually assigned requirements from roadmaps, not features. This means they get no advantage from using the timeline board as the board requires a feature to be assigned to the team to then nest the requirements
...
The ability to collapse\expand all on the Teamwork board and Backlog management board
What is the challenge?
When there is a large number of groups on the Teamwork board or Backlog management board, you have to manually collapse every group. For example, the product work on the backlog management board may have 30 releases, each ...
What is the challenge?
The Cycle and lead time report takes broad strokes at how much time it takes for the team to complete work but doesn't allow us to drill into types of work
What is the impact?
We aren't getting data to help inform fu...
What is the challenge?
Currently, you cannot move the Team order around within a Team line as you can with Workspaces in a hierarchy. When setting up PI's I'd like to be able to rearrange the Team order on my Program Board
What is the impact...