Link type "contains" definition

[Cheng, Qi]

Hi I am trying to understand the link type "Contains" and when it is appropriate to use this relationship vs creating child issues under a parent story. 

[Walter Buggenhout]

Hi @Cheng, Qi and welcome to the Community!

The link type contains is not out-of-the-box Jira. Which is perfectly fine, by the way, but it means someone in you organisation or a marketplace app has added it to your instance. The person who introduced it should be able to tell you what the idea behind it actually is.

Sub-tasks to stories may have benefits, in that you can more easily manage the completion of stories in a scrum board e.g. You won't be able to consider a story completed in a sprint while there are still open subtasks in it. Linked issues don't have that power. But that's just one thing I can think of - I guess the main thing to do is try and find out why the concept was introduced in your organisation and see if you can reach work agreements around that among your team(s).

Hope this helps!

[Cheng, Qi]

Thanks! I was using parent task and sub-tasks structure to maintain grouping of related tasks. But then I realized that I can't really roll up the story point estimates to the story level, which makes the burn-up report useless. So now we are elevating our sub-tasks to stories but I still need some sort of grouping. I am now link what used to be sub-tasks (now stories) to the main story and also use the same label for all of the story the group. Does this make sense to you?