Better handle open tasks when issue is closed

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Opportunity

When an issue is closed with tasks still in an Open status, simplify the ability for users to maintain the appropriate status of subordinate tasks.

This could mean:

1. Tasks are automatically closed
2. Users are prompted to close tasks
3. Users are prompted to close tasks OR promote tasks to a work item type 1-level up in hierarchy (e.g. issue)

Potential use cases

An issue is broken down into tasks, however the decision is made to consider the work done before all tasks are complete and follow up on the rest. Promoting those tasks will allow this "Follow up" behavior.

An issue is broken down into tasks, and the work is quickly completed by one engineer. Rather than marking each task as closed, they can close the issue and tasks all at once.

Considerations

• How would first class statuses affect this?
  • Assumption: one or more status categories will always indicate items that are done, e.g. Closed/Cancelled, and assigning a status from those categories could follow the same pattern
• Should this behavior be mirrored for other items in the hierarchy, e.g. epics > issues (#8043 (closed))?
  • What if any differences exist for "leaf node" items like tasks?