RELATED IDEAS
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories.
It will automatically send and the only other option right now to prevent this is the manual review, approval, and sending of items to integrations across the board. You can't simply have requirements in a draft state until you are ready to send like you can with features and epics. This diverges from Aha!s current design paradigm for that workflow in regards to work items.
Please implement this as soon as you are able, it's rather tedious having to manage it the way it is now. I either have to go through and approve everything manually, picking out the ones that aren't ready or I have to change the types in Jira, then go back and re-link them in Aha! It's not a good system.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
5
MERGED
Allow children of integrated items to remain not integrated until ready
I integrate our epics (master features), features, and PBIs (requirements) with DevOps (previously known as TFS). Often, I want to insert a new PBI (requirement) but I don't want it to be pushed to DevOps until it's fully built-out and ready for t...
3
Future consideration
3
MERGED
Manual Sending of Requirements to GitHub (2.0 Integration)
We have a complex portfolio of many products and many GitHub repositories. Often, we will want to break up the feature into requirements and send them to different repositories where different teams can work with them. However once a feature is in...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved
Because we are a non-dev team using Aha! and Jira, we have repetitive work that we do stemming from ideas. We are promoting those ideas to requirements and those requirements automatically create stories. The system does not know if that requirement is ready or not and just assumes it is and integrates it to Jira. We actually have a story with sub-tasks ready to be integrated with a requirement when the idea comes through but with auto-creating the story, we are unable to integrate the requirement to an existing story. This causes the hassle of dropping the integration, deleting the story it created, and then linking the requirement to the existing story. Would like for this to act like a feature and not send automatically to Jira but let us pick what we want to do. If there are others that like it automatically to create a story, maybe it's the option of opting in or out of auto generating a story in Jira.
This is a pain point for our team as well with our Azure DevOps integration. It seems to be the one issue we're unable to find a convenient workaround for.
Thank you,
Beth