Skip to Main Content
Status Future consideration
Categories Features
Created by Dale Crane
Created on Sep 30, 2022

Restore the remaining estimate when a Requirement is moved from Shipped back to In Development

When a Requirement is shipped the remaining estimate will go to 0, but if that Requirement is re-opened then it will stay 0. Is there a way to restore the remaining estimate when a Requirement is re-opened?

  • Attach files
  • Admin
    Nathaniel Collum
    Reply
    |
    Oct 4, 2022

    Thanks for sharing that additional context! Given that flow, I think it makes sense to reopen this idea.

  • Guest
    Reply
    |
    Oct 4, 2022

    Hi, as a work around, this manual fix seems to work. However, the status change would be coming into Aha from Jira as part of an integration and there would be nothing to prompt somebody to go in an make this manual change. The teams who manage the work in Jira are not the same as the teams who manage the roadmaps in Aha. That's the point of the integration. Automating this process makes the most sense and would save us from having to setup some kind of reconciliation of completed story points between Jira and Aha. Hope that makes sense. It's a real need.

  • Admin
    Nathaniel Collum
    Reply
    |
    Sep 30, 2022

    It sounds like the workspace is set to add any remaining work as logged time when the requirement is shipped.

    When you move the requirement back to In development, you can manually delete this logged time. Click hover over the "Actual effort" field and click Time tracking history.

    Then click the little blue trashcan next to the logged work.

    Please email us at support@aha.io if you have any trouble with this.