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
What is the challenge? Companies that use both Rally and Aha! ideas must go through extra steps to send information between the two systems. For example, if a small fix comes in as an Aha! idea, it must first be promoted to a feature or requiremen...
Dale Potter
3 months ago
in Ideas
0
Future consideration
Who would benefit? everyone What impact would it make? limits information leakage and information misuse to parts of the organization who don't need to see in progress epic development before it's put in an official release How should it work? wit...
paul raisanen
10 months ago
in Account settings
0
Future consideration
It will show sprints as a roadmap and will be able to give agile team more clarity.
This will benefit Agile / Scrum Teams.
A sprints view roadmap added to both Features and Release sections or once can select between timeline/calendar view or spri...
Guest
over 8 years ago
in Agile reports
10
Future consideration
Capacity planning - sync functionality available for initial and detailed estimates
Taking an initiative level as an example, for initial estimates you can view the capacity planning based on allocation across teams, you can further allocate to individual/s within that team if you know who will be working on the initiative. Once ...
Ruth Gardiner
about 2 years ago
in Capacity planning
0
Future consideration
When you are using calculated columns, and want to check if a 'value type' field such as a date is null, there isn't a clean way of comparing the value to null. For example: If a date is blank, return "Not set", else return the date formatted as a...
Guest
over 5 years ago
in Reports
3
Future consideration
Allow Release Date (internal) and Release End date (date range) to sync
Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...
Bonnie Trei
about 1 year ago
in Releases
1
Future consideration
As we continue to expand our use of Aha, one issue that has come up is that within a given product, there are different types of work/requirements that require different types of information. We're adding more and more custom fields, and it's star...
Zach Rose
about 8 years ago
in Features
8
Future consideration
Expand/Collapse Release View to include Requirements
It's critical for our teams to see Features AND Requirements on the Release (Overview/Details View). You should be able to continue expanding down the hierarchy from Epic > Release > Feature > Requirement all within the Gantt.
Guest
about 6 years ago
in Releases
7
Future consideration