11 ms·

Closed doesn't mean resolved, it means closed. Closing issues just shifts them to another tab, doesn't remove them entirely. What you propose, a filter to hide

by gochi 3y ago

Closed doesn't mean resolved, it means closed. Closing issues just shifts them to another tab, doesn't remove them entirely. What you propose, a filter to hide these, is exactly what has been done just through the official open/closed filters.

layer8 3y ago
This is not accurate. When searching for issues, users won’t find closed issues by default. When issues are linked, closed issues are rendered differently (struck through). You can’t comment on them anymore without reopening them, and reopening them is often discouraged or not enabled at all. It is a drastically different state.
- eddythompson80 3y ago
  most of that is not really true. where are closed issues rendered struck through? It's up to the repo to lock closed issues or not, and it doesn't appear this repo did that.
- rimunroe 3y ago
  Wait what? Since when can’t you respond on a closed issue without reopening it? I’ve partaken in lengthy discussions on closed issues without them reopening. Obviously you can’t reply to locked issues of course, but that’s a separate thing.
- rezonant 3y ago
  Either you are thinking of other project management tools or assuming that some of the "stale issue locking" and automated issue management tools that some larger projects use are default. On GitHub, it is true that the Issues search shows only open issues by default, but I think users are quite aware that they may need to search for closed issues, especially since it's unlikely they are on the absolute latest version of a package, especially when debugging problems in production. Additionally, some projects close issues once the mainline has addressed them even if the fix isn't in a released version. GitHub does not render closed issues as struck through, and it does not by default lock conversations on closed issues. EDIT: I am not taking a side on whether or not it's a good idea to do this sort of "bankruptcy" mass close.
  - ImPostingOnHN 3y ago
    > On GitHub, it is true that the Issues search shows only open issues by default, but I think users are quite aware that they may need to search for closed issues I think users are quite unaware, given how we have no evidence they're quite aware, and the normal thought process is "closed == resolved" (fixed, wontfix, etc) A normal thought process would be to close individual bugs as you confirm they aren't present in the new version – the end user already bore the burden of writing a bug report, and you owe it to them to actually determine if the issue is resolved before closing, even if the resolution is "wontfix". Closing bug reports without actually caring about whether they were resolved is giving the finger to your users. Why even have bug reports at that point? As far as users are concerned, you'll just close any new ones for some new reason anyways, based on your track record. Now: new version, all bugs closed. Next: new name, all bugs closed. Then: new logo, all bugs closed. After all, you close whatever bugs you want, whenever you want, for whatever arbitrary reason you want. And why not? It's your repo. Why does it matter if the bugs are fixed or not when you close 'em? You got a new thing! Close all bugs!
    - ahtihn 3y ago
      > and you owe it to them Stop right there. It's an open source project. You owe the users absolutely nothing.
      - cwillu 3y ago
        If you perform marketing and/or evangelism for your project, it's not at all obvious that you owe your users nothing.
        growse 3y ago
        The act of marketing software doesn't invalidate the license, which often explicitly states that the software comes as-is and free from warranty / support.
        3y ago
- blitzar 3y ago
  In my project a ticket that is open / closed / tagged timbuktu means whatever I want it to mean. Personally I am not going to assume that people are competent enough to check the open issues but too lazy to check the closed issues, or simply too dumb to understand a comment like "closed because I am not going to fix this".
Falkon1313 3y ago
Closed does mean resolved. One way or another. If it's not resolved, it's still open. If the ticket was improperly marked closed, that just means someone else has to create a new ticket for the unresolved issue.
- growse 3y ago
  "wontfix" is a perfectly good issue resolution.
  - ncruces 3y ago
    I started closing issues unceremoniously with a maybelater tag. If I won't be working on it, if no one is working on it, I won't leave the bug open. Either someone shows up and decides to put up the legwork or it gets closed, even if it doesn't cross the threshold of wontfix (i.e. I won't accept a fix).

by gochi 3y ago

layer8 3y ago

This is not accurate. When searching for issues, users won’t find closed issues by default. When issues are linked, closed issues are rendered differently (struck through). You can’t comment on them anymore without reopening them, and reopening them is often discouraged or not enabled at all. It is a drastically different state.

eddythompson80 3y ago
most of that is not really true. where are closed issues rendered struck through? It's up to the repo to lock closed issues or not, and it doesn't appear this repo did that.
rimunroe 3y ago
Wait what? Since when can’t you respond on a closed issue without reopening it? I’ve partaken in lengthy discussions on closed issues without them reopening. Obviously you can’t reply to locked issues of course, but that’s a separate thing.
rezonant 3y ago
Either you are thinking of other project management tools or assuming that some of the "stale issue locking" and automated issue management tools that some larger projects use are default. On GitHub, it is true that the Issues search shows only open issues by default, but I think users are quite aware that they may need to search for closed issues, especially since it's unlikely they are on the absolute latest version of a package, especially when debugging problems in production. Additionally, some projects close issues once the mainline has addressed them even if the fix isn't in a released version. GitHub does not render closed issues as struck through, and it does not by default lock conversations on closed issues. EDIT: I am not taking a side on whether or not it's a good idea to do this sort of "bankruptcy" mass close.
- ImPostingOnHN 3y ago
  > On GitHub, it is true that the Issues search shows only open issues by default, but I think users are quite aware that they may need to search for closed issues I think users are quite unaware, given how we have no evidence they're quite aware, and the normal thought process is "closed == resolved" (fixed, wontfix, etc) A normal thought process would be to close individual bugs as you confirm they aren't present in the new version – the end user already bore the burden of writing a bug report, and you owe it to them to actually determine if the issue is resolved before closing, even if the resolution is "wontfix". Closing bug reports without actually caring about whether they were resolved is giving the finger to your users. Why even have bug reports at that point? As far as users are concerned, you'll just close any new ones for some new reason anyways, based on your track record. Now: new version, all bugs closed. Next: new name, all bugs closed. Then: new logo, all bugs closed. After all, you close whatever bugs you want, whenever you want, for whatever arbitrary reason you want. And why not? It's your repo. Why does it matter if the bugs are fixed or not when you close 'em? You got a new thing! Close all bugs!
  - ahtihn 3y ago
    > and you owe it to them Stop right there. It's an open source project. You owe the users absolutely nothing.
    - cwillu 3y ago
      If you perform marketing and/or evangelism for your project, it's not at all obvious that you owe your users nothing.
      - growse 3y ago
        The act of marketing software doesn't invalidate the license, which often explicitly states that the software comes as-is and free from warranty / support.
        3y ago
blitzar 3y ago
In my project a ticket that is open / closed / tagged timbuktu means whatever I want it to mean. Personally I am not going to assume that people are competent enough to check the open issues but too lazy to check the closed issues, or simply too dumb to understand a comment like "closed because I am not going to fix this".

Falkon1313 3y ago

Closed does mean resolved. One way or another. If it's not resolved, it's still open. If the ticket was improperly marked closed, that just means someone else has to create a new ticket for the unresolved issue.

growse 3y ago
"wontfix" is a perfectly good issue resolution.
- ncruces 3y ago
  I started closing issues unceremoniously with a maybelater tag. If I won't be working on it, if no one is working on it, I won't leave the bug open. Either someone shows up and decides to put up the legwork or it gets closed, even if it doesn't cross the threshold of wontfix (i.e. I won't accept a fix).