Scenario: We have created a portfolio plan which is set to use hours as the estimate method. After we complete planning for an initiative, we create the Epics and stories in Jira and then use the option "Marking child items as complete" to close the planning of the the initiative in portfolio and track the progress via Jira sprints and boards. We believe this option would just hide the items in the portfolio. We like this idea of this option because we want a way to indicate planning is done but we can still see what we had planned by selecting to show these items using the status filter.

When I select the option "Mark child items as complete" portfolio I found it is resetting the estimate of the stories in Jira. Using this option resets any hours of work the team has logged for the stories setting it back to the original estimate. This causes a blip in the burndown and very sad engineers.

My expectation is that marking child items as complete in portfolio would not update anything in Jira.

To repro:
Create a plan with the estimates set as hours.
Create one initiative, one epic and a few stories. Set estimates on the stories in portfolio
Use the open to create and link new issues in jira
Open the new stories and log work for each one.
Return back to portfolio and select the option "mark child items as complete" at the Epic level
Return back to the stories and see the remaining estimate is set to the original estimate.

Is this expected? Are there other things that the mark child items as complete does that I should be mindful of? Is using this option in the scenario I have articulated valid?