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
Add standard date fields to requirements in Aha! Teamwork
What is the challenge?
The marketing team is moving into Aha! Teamwork. We are excited to gain more visibility into requirements by tracking them on the workflow board.
Much of our work is date driven. Think GtMs, blogs, social posts, SBs. This ...
Claire G
5 days ago
in Delivery
1
Future consideration
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
about 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
about 3 years ago
in Delivery
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...
Allow multiple assignees on Features and requirements
What is the challenge? Many teams have more than 1 person working on something. For example a couple of devs and a tester could be working on a complicated feature together. We currently can't do that. Additionally for performance reviews it's nic...
Mike Lowery
12 months ago
in Sprints
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
almost 3 years ago
in Workflow boards
2
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'...
Clark Milner
over 3 years ago
in Application / Delivery
0
Future consideration
Assigned to field on team workflow board - Default (unassigned) user
What is the challenge?
When on the Team work board and selecting your team members in the 'Assigned To' field, unable to select 'Default Unassigned' user. We would like to be able to see all work assigned to the team but not assigned to a user o...
Scott Bishop
5 days ago
in Workflow boards
0
Future consideration
Support advanced filtering (custom fields) on the workflow board
I want more control over filtering cards on the workflow board. For example, I'd like to be able to filter all of the cards based on the value of a custom field I've added.
Mark D
almost 4 years ago
in Workflow boards
2
Future consideration