Skip to Main Content
Status Future consideration
Categories Jira
Created by I R
Created on May 5, 2023

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.

  • Attach files
  • +1
3 MERGED

Manual Sending of Requirements to GitHub (2.0 Integration)

Merged
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...
Guest over 4 years ago in GitHub 0 Future consideration