Currently, when using a public portal, public portal users will not receive comment notifications when other public portal users comment on ideas they have created. Notifications will only happen when an administrator comments on an idea, or if a ...

Currently in the Idea Form there is no way to have a field where we have pre-defined values and new ones could be added. (predefined tags with new values would work as well, that's not available either.) Would really appreciate to have one such fi...

Currently, record relationship field types can't be sent to Jira. We'd like to be able to see these fields in Jira so we can report on them.

Part of our process for writing features is to essentially create a living document using the feature layout and custom fields. We created a Use Case(s) custom table that we turned into a one-to-many relationship custom field as each feature could...

Who would benefit? Our company's 750+ workspaces What impact would it make? If not resolved, this can cause damage, manual work to re-create Aha! <> Jira integrations, and work becoming out of sync between the two. How should it work? We oft...

In order to maintain consistency across the product hierarchy, it is important to keep control over the naming and organization of product lines and products. In many cases some users should have administrator access to make customizations for the...

If a report returns no data then the notification shouldn't be sent via email. It should only send the notification if there is at least one row of data.

Using SAFE terminology, I have epics (master features) that relate to multiple program increments (releases). I'd like to be able to assign a master feature to more than one release at a time.

When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...

It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...