We want our backlog to represent the set of business features we have inflight at any one moment. Each of our features has a list of child tasks that are needed to deliver that business value. When using the next-gen jira board we are able to create child stories associated to any on story but we don’t have a good way of visualizing these in the backlog. We would like to avoid having technical tasks clog up our backlog.
For example say that we want to deliver a feature that allows users to pay online for a product. Our road map will state this in the highest level of business value ( customers can pay online). Our backlog will be more specific , customers can see how much they owe. The backlog ticket for allowing customers to see how much they owe has several units of work, child tickets, each with its own set of dependencies, any of which could be blocked. Moving our parent backlog ticket to a blocked state when one of its child tickets are blocked does not appropriately describe the work being done.
I suggest that there be some way to show info about child tickets on the parent. That way we could show that our feature for providing customers how much they owe could show that 1 child ticket is blocked, 1 is in progress, and the others are not started and so on.
