For things that touch intrinsic parts that affect multiple features. A non-exhaustive list is things such as colour codes, data storage or configuration files
Tickets that are primarily for discussion. Work tickets should be created and linked to their parent discussion but no work should be done directly against a discussion ticket
Any change that adds a new feature to an existing set of features or updates any existing features, such as adding a new cmdlet to a collection of existing cmdlets
Tickets that introduce new features or change existing functionality that will require documentation to be updated. This can be changes to public names, or changed behaviours