Commit 340a36a9 authored by Alain M. Lafon's avatar Alain M. Lafon

Blog post: Hide "Close issue" button for issues on a Github project board

parent 6f2b2e98
Pipeline #5888 passed with stage
in 9 minutes and 53 seconds
title: Hide "Close issue" button for issues on a Github project board
authors: Alain M. Lafon, Alex Mihov
category: "coders tip"
date-published: 2019-07-07
- github
- project management
- css
uuid: 2c3c8961-f09d-4293-bb15-2a515d2da14f
description: >-
Have you accidentally closed an issue on Github in the projects view? Then this blog post is for you.
featured-image: /img/2019/07/accidential_close_issue_on_github.png
Many people and companies are using Github issues for project
management. With the new [projects
feature the transparency for managing a project have been greatly
improved. It gives similar options to established tools like
PivotalTracker or Trello - basically, you can create a basic custom
Kanban board.
There's one little UX pitfall into which I see people stepping over
and over (I'm no exception here). If you've seen issue updates like
this, you know what I mean:
The reason is that when working in the /project board/ view, the
preview of an issue has "Close issue" as primary call to action.
During planning and meetings, people move from issue to issue and want
to "close" the current issue, so that they can go to the next one.
However, this doesn't close the preview (the little 'x' on the top
right does that), but it closes the issue. Here's such a screen:
The remedy is easy. Modern browsers have been shipping with it since
the early days: User Style Sheets! If you don't know where they reside
on your system, [this
explains how to add them to different browsers.
Just add this snippet of CSS to your user style sheet, restart the
browser, and the "Close issue" button will be gone.
Happy project planning!
/* Do not display Github Issue "Close" button in projects view */
button.js-comment-and-button {
display:none !important;
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment