Workflow boards

When starting a sprint, the rank/order of features will persist on the workflow board. As soon as I click and drag the order on the sprint board, these changes do not persist on the workflow board.

We have a single Develop team, but we would like to have separate active sprints (in parallel) for that team to work on two platforms (Android and iOS). The main reason behind having separate sprints for both platforms is having better visibility ...

Users can prioritize work in Aha! Develop only by ordering the features. Sometimes, we have emergent work appear that doesn't follow our typical prioritization process. We need to highlight these issues on the workflow board so the team has the ab...

My team plans out several sprints in advance. When a developer finishes their tasks early during a sprint, I'd like for them to pull work from an upcoming sprint. The sidebar in Aha! Develop allows access only to the prioritized backlog. I'd like ...

Develop Contributor Role - Grant permission to the Develop Contributor Role enabling this role the ability promote Roadmap Ideas into Develop User Stories.

When I filter out features the board still has the feature count in the column, if you only work with requirements and want to add WIP limits, then the extra "hidden" data types still count towards that limit and show up in the column totals. Hide...

There is a fundamental flaw in how you calculate cycle time in develop. It calculated from the 1st in progress step on the workflow. If you rigidly follow each step then it would work fine, but in Kanban you can skip steps if they don't apply. You...

I'm finding my view of epics, features and requirements on a board very muddy. What I want to know is:1. How are the features progressing and who is taking responsibility for each?2. For each feature, how are its requirements progressing, and who ...

Overview Teams using Aha! Roadmaps + Develop find that people get confused by the two different status fields: Workspace status Team status We should improve the UX to better represent that the team status is (typically) a more granular breakout o...

Seems to be a bug where the number on the column, which used to indicate the count, is not accurate: