better redmine integration - requirements are children of features, and tasks are children of requirements

redmine integration is very helpful and needed.

 

"When a feature is copied to Redmine one issue will be created for the feature. If the feature has requirements then each requirement will also be sent as an issue."

 

there should be a way of reflecting aha's hirarchy in redmine as well.

  • features are children of releases ( at the moment, they are simply an item of my choice - but they are the same as a requirement)
  • requirements are children of features
  • tasks are children of requirements

if i really want to use aha to delegate tasks to my dev team, they need to understand this hirarchy, not just receive a bunch of "tasks" or "issues" (or whichever tracker you use...)

 

 

 

  • Michael Martini
  • Dec 7 2015
  • Unlikely to implement
Release time frame
  • Feb 4, 2016

    Admin Response

    As you had described, the Redmine integration allows individual features to be sent from Aha! to Redmine. It also allows requirements to be sent with features as part of an issue (when they are present). To-do's, however, are not part of this hierarchy as they can be related to both features and requirements.

    At this time, based on current priorities and community feedback, we are unlikely to make changes in this area. We hope you can understand.

  • Attach files