Automation: support setting a date field to a value relative to another date field
I wanted to create an automation to update the external release date to match the release date on a release when that changes. Arguably we should just do this automatically already... but I was hoping that Automation would solve the issue After se...
I would like to be able to copy a custom field, for example from Features to Requirements. I have several custom fields for Feature, then when I want to create a requirement from Aha! it complains those custom fields are not available,
When a user logs into Aha!, the first page they see is the page "How Aha! works". Our users are reporting that this is confusing, as they want to navigate to a page within the product itself (i.e. Feature Board or Releases Overview"). Users arrivi...
When editing Tags list on "Config Tags" page, having the ability to bulk edit Tags (Delete specifically) would be very handy as the tags list could become very lengthy and removing multiple tags (with a criteria e.g. Tag starting with RFP#) takes ...
Allow custom statuses to inherit from product line
The update to allow customizing the default status is great.
However, it doesn't solve the problem where we have multiple business units in a single account and each business unit has their own distinct workflow for their portfolio of products.
Se...
Copy an existing workspace when creating a new workspace
When creating a new portfolio (product) line and multiple products (workspaces) in it, I need to ensure that all these new products are configured identically. The more complex and customized the configurations, the more error prone and tedious it...
Contributor should not have permission to change a Workspace name
One of our Contributors accidentally changed the name of a Workspace. They were unaware that they would have permission to do so, and they did so by mistake. We would like to be able to disallow Contributors from changing (or accidentally deleting...
Automation: Allow for Workspaces to inherit automations from Product Lines
I work in a group that has many workspaces. We would like to be able to define automations at the Product Line level that will impact all workspaces underneath it or at least be available to the workspaces underneath it.
Currently, you can create custom terminology for most of the menu's in Aha and other terminology. I would also like to be able to rename the Roadmap menu (for example to Reports, as this is more meaningful for our company) as the new Roadmap menu ...
Ability to apply a workspace template to multiple workspaces in bulk
Workspace templates are a great way to encapsulate workspace configurations into a template, so that we can quickly spin up new types of workspaces. However after creating a new template, we have a need to apply that template to a large number of ...