Allow Product Owners (not Admins) to configure/add sub Product Lines within Product Lines that they own
In our large organization, top-level Product Line owners should be able to add new, sub-Product Lines without needing Admin access. Admins have the power to change many global settings that could impact the work of others in the organization. I'd ...
Gary Spencer
almost 10 years ago
in Account settings
4
Will not implement
Who would benefit? Everyone who collaborates in multiple Notebook workspaces What impact would it make? Huge time saving not having to create or learn new folder structures in different workspaces How should it work? Similar to custom layout - be ...
Rob F
about 1 year ago
in Notes
0
Future consideration
It would be useful to be able to show the workspace name on items on the calendar reports. We managed a portfolio of products in Aha! and would like to use the calendar to highlight upcoming releases. However, we aren't able to indicate which work...
Max O.
over 3 years ago
in Calendar
0
Future consideration
When user is working on List Report and changing the records data in panel view records after closing the record list report is not refreshed. User need to do it manually. It would be great if the line with record which was updated will be updated...
Guest
almost 5 years ago
in Reports
2
Future consideration
When changing custom layouts and fields, it would be very useful to be able to see a preview of what the change will look like before saving and impacting multiple workspaces. Right now to work around this use our playground area when changing exi...
Nerissa Muijs
over 2 years ago
in Account settings
0
Future consideration
The problem I'm trying to solve with this idea is that the internal release date can only be a date. This is challenging for me and my stakeholders as we have to leverage the external release date as our primary value. The reason being, I am an ad...
Guest
over 3 years ago
in Releases
1
Future consideration
Track features that moved out one release into the next
It would be really useful to track features that are prioritised into a release but then drop out, either going into a subsequent release or back into the backlog. Currently this is captured manually but features fall through the cracks when peopl...
Guest
almost 5 years ago
in Features
1
Future consideration
Often I'm working a feature that has many requirements on it. Some of those comments can have very large discussions on them, making it hard to scroll to the next requirement. If I could collapse the comments, it would make it easier to have multi...