RELATED IDEAS
Persistent filters for integrations and incoming product updates
Using JIRA integrations, I have an Aha product that spans several JIRA projects. To work with this I have set up an integration per project with a specified JQL filter. For example my filter could include "priority = high". Other products throughout our organisation might use other filter parameters that may or may not conflict with the original.
This memo is to request that integration setup be able to specify specific constant filters that would channel filter incoming webhook traffic to a solely a single product. Updates for products would continue to use the filter so that unwanted JIRA issues would not be imported to each product.
5
MERGED
Remember what you wanted to import
As a user of Aha! and Jira I want help remembering what I have entered as a filter instruction when importing data from Jira so that I can more easily fine tune my filter to get the right data imported.
In the 'Import from development tool' functi...
1
Future consideration
© 2026 Aha! Labs Inc.•All rights reserved
If I manually update records from Jira, there is a defaulted JQL query. Our organization does not use statuses the same way, if the default is not cleared or replaced, no updates will happen. It seems that these instructions would be saved with the integration instructions and not something you typically change each time you update. As we roll out Aha, this is also very difficult to train multiple people to understand. Some think the default in the field is just ghost text, which adds to confusion.