Rollup child items to parent completed work field

Officially Answered

Comments

3 comments

  • Avatar
    dev

    Hi Ronnie,

    Thank-you for reaching out! 

    This is something we considered implementing in the past. However, automating this calculation would cause the Burndown charts and other metrics in Devops to display incorrect data. For example, in a scenario where Epics > Features > PBIs are organised in hierarchical order, this mechanisms would cause the Burndown to decrease by three hours for each hour logged against a certain PBI. This is because the rollup logic would cause that same hour to count against the PBI, its parent item (the Feature) and the parent of its parent (the Epic). 

    Because of these limitations we generally advise our customers to perform their data manipulation at the API level instead. Alternatively, you can find this information on our Reporting page or on the WI time tab. 

    Kind Regards,

    Andrea

    Product Owner - www.7pace.com

    0
    Comment actions Permalink
  • Avatar
    Ronnie Merkel

    Thank you for following up. I understand the constraint and potential impact to other uses. Would reporting the total work back to a different field such as a custom "Completed Work Total" prevent the negative impact you identify? Alternatively, is there a way to query this information from the API via webhook?

    0
    Comment actions Permalink
  • Avatar
    Andrea Moro
    Hi Ronnie,
     
    yes you could get this data via our APIs, however we do not support webhooks unfortunately.
     
    May I ask what product management system you are using?
     
    Kind Regards,
    Andrea
    Product Owner - www.7pace.com
    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk