Reviewer users should be able to change a feature's (or requirement's) up to a certain point
For example, We may have our engineering team (or QA team) in Aha! as "reviewers" and we would like them to participate in escalating status - such as: Engineer would say "In Development" when they start, and "Development Complete" when done. Then...
Guest
over 9 years ago
in Features
3
Will not implement
Support One to many relationship fields on Customize record cards
Why is it useful? Ability to add One to many relationship fields on Cards really helps to view the field value at glance rather than to open a record to view field values.
Who would benefits from it? Anyone who uses board.
How should it work? It...
Tej Namala
over 2 years ago
in Account settings
1
Will not implement
I have a solution A which is made up of features X and Y from products B and C respectively.
However, X and Y may also be features in solution B.
With the recent update, you’re able to view master features along with features on the feature b...
Guest
over 5 years ago
in Epic
0
Will not implement
Create competitive pricing tier for low-access users
Picture this. You're paying Aha $1800 per year for Enterprise+ because that's the tier you need. 100 people work at your company, and they have been using Zoho Projects @ $60 per year per person. You are not not not going to convince this company ...
Debbie Levitt
over 2 years ago
in Features
0
Will not implement
Ability to count total number of objects within a product
It would be really useful to be able to list/count the total number of objects (requirements, features, master features, releases, initiatives, goals) across one or more products in a single pivot report.
This could be done by making a product in...
Guest
over 5 years ago
in Reports
0
Will not implement
List view of Ideas should be separate for each product
It doesn't make sense to be in a product and see ideas from another. I know that I can filter out what I don't need, but this is unnecessary. If I wanted to make an ideas list of all or multiple products, I would just go to Reports. When clicking ...
Guest
over 8 years ago
in Ideas
3
Will not implement
Currently Documentation in the UI points at API documentation. Embedding user documentation in the UI makes more sense! https://agile-jira.ciena.com/browse/BPINV-3285
Guest
almost 3 years ago
in Ideas
1
Will not implement
Required for 0118516 - SSEET - BP BPI Scrum Team Service Front and back of rack, with device depth https://agile-jira.ciena.com/browse/BPINV-4934 Freestanding devices on Rack trays https://agile-jira.ciena.com/browse/BPINV-4935 https://cienabp.aha...
Guest
almost 3 years ago
in Ideas
1
Will not implement
Currently we only have ability to link the ticket to idea or to create idea in Aha!. But if the ticket already exists, we can not link it to existing feature or requirement.Or if we want to create directly feature or requirement, it is not possibl...
Mia Rucevic
almost 9 years ago
in Integrations
5
Will not implement