Issue resolved vs closed MVC

From: #208493 (comment 391795414)

Problem to solve

• We cannot unambiguously tell apart issues that were completed (done) from issues that were just closed - this impacts velocity & volatility calculations.
• We are working towards and ideal vision for customizable issue types and workflows. One of the concepts we would like to test is having multiple issues states & statuses (largely inspired by how Clubhouse handles this) -- &3354.

Intended users

• Delaney (Development Team Lead)
• Devon (DevOps Engineer)

User experience goal

Hypothesis: We believe that creating granular statuses (closed vs resolved) for the closed issue state will help software teams have greater clarity around what has been achieved within a particular milestone/iteration.

Proposal

1. Add split dropdown button at the top of the page and under comments with following states:
   • Resolve
   • Close
   • Abuse
2. Update state badge to include following colours:
   • Open = green
   • Closed = Red
   • Resolved = Blue
   • Moved, Promoted, Duplicate = Gray
3. Update quick actions to contain /resolve command
4. Change from Close with MR to Resolve with MR (+ associated UI change within MR)
5. Allow user to retroactively edit status of closed issue state
6. When a blocked issue is being closed, do not ask "Are you sure you want to close this blocked issue". (Continue asking when the issue is being resolved.)

Now:

• Test the concept of state statuses within our non-generic issues.
• Enable feature flag and dogfood with our group first
• Adjust velocity calculations: #208493 (comment 401383272)

Later:

• The learnings from this MVC could then be applied to extensible issues.
• We can also use these changes to potentially morph statuses into states once users were familiar with this approach.
• We could then add closed(complete) vs closed(incomplete) to boards

What does success look like, and how can we measure that?

• Adoption of closed/complete vs closed/incomplete status indicators
• Filtering within issue list, issue analytics or Iteration report on Incomplete vs complete
• Positive user feedback

Is this a cross-stage feature?

Documentation

Documentation would read something like:

• Resolved Issues count towards your Insights, Iteration/Milestone burndown/burnup and progress reporting, ...and all the things where we should only really count progress based on resolved issues.
• Issues that are Closed, Moved, Duplicated, or... are not included the following analytics and progress reports...

Yes - devopsplan devopscreate