Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Delivery

Do not allow users to bypass fixed workflows on the workflow board

What is the challenge? If you have a fixed workflow and you navigate to the epics/features workflow board, users can create new records at statuses further along in the workflow. What is the impact? This allows them to create records without goin...
Stephanie Lechner 24 days ago in Workflow boards Future consideration

Terminology in Teamwork should align with workspace initiative when relating records

What is the challenge? Currently, Teamwork does not have the ability to give custom terminology at the initiative level since Initiatives are not a record type, nor innately visible, in Teamwork. However, when attempting to create a custom lookup/...
Guest 28 days ago in Delivery Future consideration

Add option to group by custom fields on Workflow Heatmap

What is the challenge? On the Workflow Heatmap report, it is possible to group the data by a few default fields, such as assignee, estimate, and record type. It is not currently possible to group by custom field. What is the impact? Many users ut...
Maria Plotkina about 1 month ago in Agile reports Future consideration

Support Aha! Teamwork/Develop individuals splitting their capacity across more than one team

What is the challenge? Currently, individuals that need to be part of more than one team can only have one schedule. Planned work in each respective team does not consume that individual's capacity and is not visible in totality This means tha...
Terence Osmeña 4 months ago in Capacity planning / Delivery / Sprints Already exists

Default workflows for teams in a team line

What is the challenge? When a new team is added, they receive a unique workflow so that modifying the board doesn't change other teams boards However, it appears that each time a Team Line or nested Team workspace is created, new workflows are...
Julie Hunt about 2 months ago in Workflow boards Likely to implement

Pull all related requirements into sprint when feature is added to sprint

What is the challenge? Currently, when planning a sprint and pulling work, you have to drag and drop every record individually. However, you can assume that if a feature is pulled into a sprint then all related, remaining requirements would also b...
Guest 30 days ago in Sprints Future consideration

Allow the "Move to top" and "Move to bottom" right click options in Teamwork parking lots

What is the challenge? Parking lots in Teamwork can contain just as much work as a Roadmaps release creating hurdles during collaboration and planning. What is the impact? Manually having to move work items out of the way results in a lot of scro...
Matthew Raymond 3 months ago in Backlogs Planning to implement

Aha! Teamwork/Develop board filters to work the same as the Features board

What is the challenge? Currently, a team transitioning from using an Aha! Roadmaps features board to an Aha! Teamwork/Aha! Develop board cannot add any record filter, like the Features board Although there are some filters that can be included...
Terence Osmeña 4 months ago in Workflow boards Future consideration

Unify workflows and automation in a Visio-style graphical UI experience

What is the challenge? Workflows and automations are separated and managed in a tabular GUI. This makes coordinating workflows with automation integration challenging. What is the impact? Slower development, mistakes, and gaps between flow and au...
Guest 23 days ago in Workflow boards Future consideration

Timelines do not properly show dependency lines.

What is the challenge? In the "Timeline" view, when I update a dependency between two records, the dependency is added to the record, but the arrow disappears when I refresh. Describe your idea. Given I am a user When I edit dependencies in t...
Ryan Lindorff about 1 month ago in Agile reports Future consideration