As we are implementing some stories we find some things which need to be put on a backlog as technical debt, often because there are larger questions linked to other stories or features which cannot be trivially answered and would derail our sprint goals. We might be bashing out a first version and want to make sure we record things so we can manage and record our technical debt activity.
WI types such as requirements and issues had seemed like good options to keep these clearly segregated but Azure DevOps seemingly only allows you to see the following work-item types in your backlog:
I don't really like the idea of a story "xxx technical debt" and putting them as tasks on the actice story doesn't match our process - we want to mark the story complete but record debt (or other design questions) for a later iteration. And typically these are not really stories, since implementing them makes zero difference to functionality or users.
Would adding as bugs make sense perhaps? Is there a suggested direction from MS or a widely used pattern that's close to being a defacto standard?