All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5666
8
VOTE
Hide parking lot from certain user roles
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...
0
Future consideration
6
VOTE
Copy object name with URL link (rich text format)
What is the challenge? When referencing object in chat with team-mates, I have to copy the URL link and then modify to include object name (feature name, release name, etc.). What is the impact? If I don't do that, my team-mates must open the link...
5
Future consideration
13
VOTE
Read-only fields based on permissions
It would be very useful to be able to set read-only permissions for some fields (either standard or custom fields) based on permissions, or - even better - permission groups. In fact we have some fields on Features and Ideas that should be maintai...
0
Future consideration
2
VOTE
Easier way to search for shipped releases
What is the challenge? Based on the popularity of these 2 ideas, there is a pretty big need to more easily find shipped releases. https://big.ideas.aha.io/ideas/APP-I-5819 https://big.ideas.aha.io/ideas/AFPR-I-7541 The difficulty exists because it...
0
Future consideration
2
VOTE
"Remind me later' for notifications
What is the challenge? Sometimes users want to clear notifications but still need a way to come back to them later What is the impact? Improves productivity by allowing users to focus on tasks at hand without losing important reminders Describe yo...
0
Future consideration
2
VOTE
4
VOTE
Record successful updates in Aha! from Jira "update records" action
What is the challenge? Currently, there are log events for successful updates made from Jira when using the "Update Records" action What is the impact? Users have no way of knowing which records were successfully updated and what fields were chang...
0
Future consideration
10
VOTE
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) ...
1
Future consideration
24
VOTE
Make the standard tags field mappable for requirements
Both epics and features have the standard tags field mappable when setting up an integration. Requirements now have a standard tags field added to the record but it is not available in the mappings. It currently requires a custom field be created ...
3
Future consideration
22
VOTE
© 2024 Aha! Labs Inc.•All rights reserved