Parent field data disappears when Resolving a story as Done

[susan.miller]

I've noticed when Resolving a jira story as Done, the Parent field data disappears automatically.  In the history, it looks like the person resolving the story is also changing the Parent to None, but they are not, it just seems to happen on their behalf.  

[Nic Brough -Adaptavist-]

Don't estimate on sub-tasks if you're doing Scrum, it won't work.

[Avinash Singh]

Thanks.  Would you support the idea of having custom fields for the various efforts? What will be your approach ?

[Nic Brough -Adaptavist-]

Yep, create numeric custom fields for the various estimates, then I'd use Scriptrunner to add them up for display, search and reporting.

[Avinash Singh]

Thanks. I assume this will be your preference over have an individual task for each part of the work, where you would estimate the work using the native jira functionality ?

[Nic Brough -Adaptavist-]

I would tend to if parts of the work can be done in parallel, but I'd avoid putting estimates on sub-tasks if you're going to do Scrum, because that doesn't work.

[Avinash Singh]

Do u mean sub-tasks ?

Also do you have automation in place to create these tasks for every issue ?

[Mesut Yilmazyildirim]

In my company I am handling same requests but I always suggest them to split issues into small tasks. 

Now squads create different tasks for development, analysis or tests. Each task has own estimation. And team can calculate total velocity of the Squad.