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
over 4 years ago
in Epics
9
Future consideration
custom scorecard internal field change, does not trigger change event when the total result is the same
What is the challenge?
We have a situation where we have an Epic that has a custom scorecard field.
When you change some of the internal scorecard field items, and the total score result is the same as it was before, the system does not recogniz...
Arieh Stroul
about 2 months ago
in Epics
0
Future consideration
Access "time in status" detail when looking at a record
What is the challenge? When I'm looking at a record and I want to understand the progression between statuses, I have to create an ad hoc report to see what I need. This wastes time and I'd rather just see what I need within the context of my work...
Aaron P
5 months ago
in Epics
0
Future consideration
Display capacity line on Releases when looking at Epics board view
What is the challenge? When viewing the Epics on a board view, a capacity line does not appear even when "Epics" or "Features and epics" are used for the calculation. What is the impact? When estimation is done at the epic level, and epics are use...
Maria Plotkina
over 1 year ago
in Epics
0
Future consideration
Ensure features and epics roll up to an objective/initiative pair
What is the challenge? We've defined a set of objectives (goals) and a set of initiatives under each goal. But the UI allows epic and feature creators to select objectives and initiatives that are independent of one another. What is the impact? Th...
Sandy Kobayashi
about 1 year ago
in Epics
0
Future consideration
Ability to Configure Epic View as Default for all workspace views (Board / Prioritization)
Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
Hank Liu
over 1 year ago
in Epics
0
Likely to implement
Create New Initiative Directly from an Existing Initiative
What is the challenge? Product Leaders cannot create a new Initiative (we refer to them as Epics at Thrivent which is one product line lower) directly from an existing initiative in Aha. You can only add existing initiatives. This is challenging f...
Guest
6 months ago
in Epics
0
Future consideration
Add "For workspace" field for epic layout that reflects the release's workspace
What is the challenge? Users need to click into a release to see which workspace an epic's sits in. This is not very intuitive for new users and adds an unnecessary extra click to view a critical piece of information. Release has many definitions ...
Max Klin
5 months ago
in Epics
1
Future consideration
What is the challenge?
Currently have to copy/paste from the AI writer into an open text field
What is the impact?
Death by a thousand paper cuts. Likely expending 20 hours per week to create customer friendly product descriptions
Desc...
Guest
2 months ago
in Epics
0
Future consideration
Allow epics to inherit prioritisation scores from features
What is the challenge? We prioritise features, not epics. However, it's still useful for many reasons (e.g. reporting) to have a prioritised view of epics as well. There's no way that we will spend the time to score epics separately though. What i...
John P
8 months ago
in Epics
0
Future consideration