Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #1674

Closed
Open
Created Oct 10, 2012 by Administrator@rootOwner

2.9 minor: issues list 'Resolve' button vs. issue 'Close' button

Created by: sroth80021

This is a minor usability issue, with what I think is a simple fix.

In GitLab 2.9, there is some confusion about whether the 'Resolve' button in the Issues list is the same as the 'Close' button in the Issue itself.

Since there is no 'Close' button in the Issues List, since there is no 'Resolve' button on the Issue itself, and since I dont see a way to separately filter out resolved vs. closed issues, I presume they are equivalent.

If that's the case, then it would be nice if they had the same button text and color. It would be less confusing.

Or... If there really are two states, it would be nice if both views showed both buttons, and there was the ability to filter on closed as opposed to resolved.

Assignee
Assign to
Time tracking