Close button - counterintuitive title confuses new users

Summary: The "Close" button does not have an intuitive title.

Steps to reproduce: View an issue for which you have write access. The "Close" button is toward the upper right corner of the browser window. This button closes the issue instantly. The word "Close" is too similar to the common user interface button for closing a GUI window and thus can confuse new users.

Expected behavior: The title of the "Close" button should make it clear that the button closes the Issue if the user clicks on it. I suggest that the title be changed to "Close Issue".

Version of GitLab you are running: 8.1.1-ce.1

Possible fixes: Replace the word 'Close' with 'Close Issue' in app/views/projects/issues/show.html.haml#L32

Relevant screenshot:

Title changed from Close button - counterintuitive title confuses users to Close button - counterintuitive title confuses new users

@Nordic-Harold thank you for the feedback, I would suggest Close btn is confusing because there is New Issue Btn neighbouring it, so call to actions are messed up by wrong location. There are some IA changes coming with interface updates, and we will take your feedback into account.

Please use GitLab labels next time so I can find UI/UX related issues easier. ^^

Added ~12742 ~19492 labels

This is also incredibly confusing when commenting on a Merge Request. The "Close" buttons context makes the user believe that it will close the comment area, but instead it closes the entire MR. In my view these buttons should say either "Close Issue" or "Close MR" to make it more clear what action they will take.

@JobV what do you think about changing Close to Resolve? My feeling is that Resolve verb gives more fulfilling context in the performance sense, than Close.

And I would definitely change the sequence to Edit => Close(Resolve) => New Issue

/cc @sytses @dzaporozhets

@creamzy I think it's a good idea. Can you put it on the agenda to discuss with a link to this issue?

@creamzy @JobV One thing I don't like with "Resolve" is that we have 2 different words explaining one issue state. I rather add explicit "Close issue" title for button instead.

@dzaporozhets alternatively, it'd be Resolved

@JobV I dont want rename every single piece of UI from Closed to Resolved

You might close an issue even when it is not resolved. 'Close issue' might be acceptable.

I agree with @sytses. Closing and resolving can mean different thing. Issue can be unresolved but closed. Ex JIRA has status (Open, Closed) and Resolution (Unresolved, resolved). So I propose not to use Resolve

@dzaporozhets @sytses @JobV Close Issue it is, and we keep the sequence as it is as well

@creamzy good. Move this issue to Frontend and put 8.6 milestone

Based on the discussion above

Milestone changed to 8.6

Added frontend and removed ~19492 labels

This should be fixed by now.

Milestone changed to 8.7

Looks like this has been fixed

Status changed to closed

Button is now "Close Issue" so we are good to go.