RELATED IDEAS
Track effort (estimates) to prepare features for JIRA separately
When Aha!-JIRA integration is enabled, updating the features estimates on one of the tools, will cause an update on the other.
We suggest to have the possibility to un-map the estimates fields between the 2 tools. So updating on one tool won't affect the other.
We would like to have separate estimates on features on both JIRA and Aha!. Where these estimates don't relate to each others.
Aha! users (Product managers), they use estimates in Aha! to bring the feature to "ready to develop" state. While JIRA users (developers), they use JIRA estimates to bring the features to "ready to ship" state.
In our case, both estimates are different and shouldn't overlap.
-
ADMIN RESPONSEJan 22, 2016
A workaround for this scenario would be to leverage custom fields. It's now possible to sync custom fields between Aha! and JIRA. You can create custom fields to set estimates and this is a two way integration.
Please see this blog post for more details: http://blog.aha.io/index.php/just-launched-two-way-jira-integration-now-supports-custom-fields/
© 2024 Aha! Labs Inc.•All rights reserved
It seems like you need two different estimates, one for the preparation of the feature (i.e. building requirements) and then an estimate for the development portion. Couldn't this be handled by adding two features or two requirements tasks with different estimates?