RELATED IDEAS
Filter which JIRA issues get reflected back to Aha!
Aha! allows product managers to stay at the 40k foot level, while JIRA is used by our development team, which means it contains lots of small implementation details. If all the bugs and tasks being logged by my developers in JIRA reflect back into Aha!, It gets just as messy as JIRA, and starts to provide less value... So I'd like to be able to specify what gets reflected back (the ideal implementation would be to specify a saved JIRA/JQL search...if it's not in that query, it shouldn't get reflected back into Aha!).
Hi Rob -- please use this link: http://support.aha.io/hc/en-us/articles/204452355. We consolidated the support note. It now reviews all of the advanced customization available for JIRA and the first section is what you want to read.
The link below doesn't work...anyone have an update for the URL?
Jackpot :)
Good news. If you are using the JIRA integration (rather than JIRA via Connect) then you can control which issues are converted to features using JQL. This article describes how to do this:
http://support.aha.io/hc/en-us/articles/202165449-Customizing-what-issues-are-automatically-created-...