Work Item Combination Naming

I'll typically do a big chunk of build work for a sprint in a dev sandbox, and then deploy to a UAT sandbox for testing. As you'd imagine, there's a variety of small bugs that come with it, which require new work items.

I've gotten in a good habit of naming work items very strategically to keep track of what work item is what, but ultimately to deploy these I have to combine them. The combination works, but the resulting work item name is usually the last bug name and it's not super helpful. Would love some more custom options for controlling work item names.

(I've hacked this by just going to the work item record in the backend, but would love to not have to do that).

Also, if there was way to visually see which work items had dependencies on a each other that would be HUGE!

The issue does not name files, tests, or entry points. Start by examining how combined work items are named and how dependencies are represented, including the backend work-item record mentioned in the report; done would require a defined naming-control option and a way to visualize dependencies.

Written by the indexing model from the issue text.