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!).


  • Ely Greenfield
  • Oct 31 2014
  • Already exists
Release time frame