RELATED IDEAS
Create an integration at a requirement level
It would be useful to be able to send requirements to different integration points. i.e. if we use requirements for a design task these could be sent to Trello. and Development tasks could be sent somewhere else - Jira. Or to two different projects in the same system.
Needs:
1. Ability to send specific requirements to the right teams in dev systems. E.g.: front end, backend or database teams in JIRA (or other development systems, e.g. Rally.)
2. Ability for status to be updated back to Aha! from each dev teams system, e.g. JIRA project.
3. For JIRA, ability for new "requirements" created in JIRA to be auto-created in Aha!
-
ADMIN RESPONSEFeb 27, 2019
Features are sometimes moved from one project to another in your development system by the engineering team. Now you can ensure they remain up to date no matter what project they end up in. In our Jira and Rally integrations, requirements will stay in sync with the proper parent:
When moved to a different project after sending
When sent directly to different projects
Check out the blog post to learn more.
4
MERGED
Additional Mapping option on Rally Integration configuration to specify where parent features/ child user stories map to
We would like to see the ability to send the parent feature to one Rally parent project and child user stories to a different Rally child project. This enhancement is needed in order to perform our team's rollups (as features live at the parent pr...
0
Shipped
This is exactly an issue were running to now as well; with multiple teams working on a single feature, within different Jira projects, it's very cumbersome for us to manage the requirements for them.