Automation of feature to another release based on custom field
Who would benefit? Product Management Team What impact would it make? Ability to cut down on manual work, reducing mistakes and time spent on administrative work How should it work? Under automations, be able to set a rule as such: When a feature ...
Danielle Martinez
about 2 years ago
in Automations
3
Future consideration
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
about 4 years ago
in Automations
1
Future consideration
What is the challenge?
If a large text panel is created and the text toward the bottom of the panel needs formatting, the text editor is not viewable and available to use.
What is the impact?
Makes it difficult or impossible to format the ...
Tracy T
6 months ago
in Reports
0
Future consideration
Allow admins without a paid license to manage workspace hierarchy
What is the challenge? Some teams have central admins who do not manage work in Aha!, just help configure it for end users. These users have full admin permissions and help administrate the account. This is fine for most settings, but if a customi...
Max Robbins
7 months ago
in Account settings
0
Future consideration
What is the challenge? Often, teams will create release templates when they have repeatable projects that follow similar steps. But release templates just include phases and todos. Many teams have more complex template needs for their project work...
Max Robbins
about 1 year ago
in Releases
1
Future consideration
Allow requirements to inherit the color of the activity type in Aha! Teamwork
What is the challenge?
The marketing team is moving into Aha! Teamwork. For the most part we are planning to visualize work at the requirements level.
We love that you can add icons and color activity cards by type. But unfortunately we do not ...
Claire G
6 months ago
in Workflow boards
0
Future consideration
What is the challenge? Idea categories are commonly used as a trigger for an automation - for example, assign idea to a specific Aha! user based on the idea category. When you use the categories field in an automation, the hierarchy of categories ...
Max Robbins
7 months ago
in Ideas
0
Future consideration
Restrict the visibility of specific custom fields to different users
We use Aha! for all our product planning, however we currently do some financial estimates outside of Aha! which we don't want to share with the wider development team. This causes us to fragment our data and use permissions in other portals as th...
Mark Gerrard
almost 5 years ago
in Epics
9
Future consideration
What is the challenge?
Assigning work, would it be Epics, Features, Requirements, or whatever item, to an individual is not relevant for us, for multiple reasons :
We might assign it from Jira
Some tasks require multiple people from the same...
Clément Pasini
about 1 month ago
in Capacity planning
0
Future consideration
What is the challenge?
We have to extract excel report of each shipped release records and save in sharepoint, lots of manual efforts in maintaining logs of each change in release (change in scope-addition/removal of features and epics when rele...
Ankush Kumar
4 months ago
in Reports
0
Future consideration