Problem: Currently, Aha permissions are primarily managed at the workspace level. This creates challenges for initiatives that are confidential or limited to specific stakeholders. To restrict access, teams often create separate workspaces, which ...

What is the challenge? Many teams use Microsoft Teams for communication, and the lack of native integration limits efficiency. What is the impact? Enhances collaboration by enabling seamless access to Aha! features directly within Microsoft Teams ...

What is the challenge? New conditional choice fields are not supported in automation rules. What is the impact? Unable to create rules based on choice field values. Describe your idea. Show choice field options when setting up automation rules.

What is the challenge? Phases tab of Releases is not customizable and provides very limited value. Name and date don't provide meaningful insight into the phases. Going into each individual phase for more information is inefficient. What is the i...

What is the challenge? When any workspace is excluded from Elle's AI controls, Elle can't read, create, or edit any report account-wide, even if the report only contains data from allowed workspaces. What is the impact? Common setups (excluding t...

What is the challenge? Currently, limiting Elle (AI Assistant) workspace access only prevents workspace record access. Workspaces where Elle (AI Assistant) access has been specifically excluded, Aha! users can still open Elle (AI Assistant) from t...

What is the challenge? It's currently not possible to show a goal's roll-up goal (i.e. grandparent goal) on a grandchild epic or feature record) The roll-up goal can often provide helpful strategic context and ensure that the correct parent go...

What is the challenge? All company employees are Aha! users and submit ideas logging in via the existing SSO. This means however that they are not treated as portal users which means that they do NOT receive portal notifications around when ideas ...

What is the challenge? The "Account activity" log shows changes made by (and applied to) users identified by their email addresses. What is the impact? Certain teams use universal emails or ID-based emails, such as "ab123@xyz.com" for SSO-based p...

What is the challenge? Aha! date fields currently expect exact calendar dates, even when teams only know timing at a broader planning level such as fiscal week, month, quarter, or year. To represent those plans, users have to manually choose artif...