RELATED IDEAS
Allow me to not sync requirements when syncing features with Jira.
We use Jira sync to keep bugs (jira bugs) and dev work (aha features) in sync and up to date. However, when the dev work gets defined (aha requirements), these requirements show up in jira (sub-tasks). I would rather not have them push into and clutter jira. Aha gives me the ability to optionally send releases and initiatives... I would like the option to optionally send requirements as well. Right now i end up going into jira periodically and deleting all of the sub-tasks.
-
ADMIN RESPONSEDec 14, 2017
We have launched an enhanced Jira integration. This integration gives you the explicitly add and remove record mappings including requirements, along with several other new capabilities including the ability to:
- Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
- Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from Jira)
- Automatically send outgoing changes from Aha! or choose to review and approve them
- Import records directly from Jira to make getting started in Aha! easy
Check out the blog post for more details.
© 2024 Aha! Labs Inc.•All rights reserved