Creator of LULs (a script which helps links to point to your instance)

Come say hi here or over at https://twitch.tv/AzzuriteTV :) I like getting to know more people :)

Play games with me: https://steamcommunity.com/id/azzu

  • 1 Post
  • 45 Comments
Joined 2 years ago
cake
Cake day: June 29th, 2023

help-circle




  • Well the reason to auto-close is that this is not an entirely unlikely resolution. When I inherited a project with a bunch of issues and started going through the backlog, around 50% of tickets were duplicates, already solved, unreproducible, etc etc

    When you’ve only got limited time, having less of those issues to analyze and then close anyway is a very valid reason. It leaves more time for fixing real issues. Of course it comes at the cost of ignoring perfectly valid issues as well, that’s why this is obviously never an optimal policy to implement, and should only be done in desperate situations.


  • That’s why the “easy way to reopen” is so important. Your concern is theoretically valid, but if tickets are usually ignored for years, then it really is a desperate situation for the project whichever way you handle it. You can decide between an endlessly growing list of issues that likely aren’t valid anymore, or pissing some users off.

    I don’t really see why it would be harder to find an existing or similar bug. You should be looking (or rather you should be automatically notified) before/during creating a new ticket for existing tickets describing the problem. If a closed ticket describes the exact problem, you should be finding that too, and then should just be able to use the easy way of reopening if necessary. You should also be able to find the workaround in there if someone posted it.

    It’s definitely not a beautiful solution, but if you implement something like this, the project is already in a desperate state, there’s not too much good choices there anymore.



  • I don’t think so. It should have an easy way of reopening - if it has, and you’re flooded with tickets on an open source project that you can’t possibly handle all, then it’s a good way to prioritize. Of course it doesn’t have an easy way to reopen here, which sucks, it’s some kind of locking instead of just closing it with a possibility to reopen.

    Old tickets have a non-zero chance of the reporter being the only one to run into it because of a weird setup/usecase (and then abandoning the project), it being fixed by other work, or probably a bunch of other reasons it could be obsolete.

    If no one cares enough to reopen it once every 6 months, then it’s probably fine to ignore it indefinitely.




  • Azzu@lemm.eetoProgrammer Humor@programming.devMicrosoft Please Fix
    link
    fedilink
    arrow-up
    10
    arrow-down
    4
    ·
    4 months ago

    It’s absolutely not a skill worth having. If you ever run into issues and need the CLI, you can always get your knowledge right in that moment. If you already can do everything with your GUI and get the same results, getting the knowledge to do it some other way is just wasted time and duplicate work.








  • Ich mein, dafür sind eigentlich Gewerkschaften und Streiks. Aber die meisten im Gesundheitswesen würden das nicht machen, weil die Patienten dann Probleme kriegen. Aber genau das nutzen Arbeitgeber halt aus.

    Der einzige Weg ist, sich zusammenzuschließen, zu streiken, und als Forderung die Arbeitsbedingungen verbessern. Ist kurzfristig für Patienten negativ, aber langfristig würde es besser. Wenn Arbeitgeber halt wissen, dass niemals gestreikt werden wird, können die Arbeitsbedingungen immer schlechter werden, und das werden sie ja anscheinend auch.

    Alternativ kannst du dich natürlich persönlich immer weigern, etwas zu tun, was du nicht tun möchtest. Wird halt wahrscheinlich auf Kündigung rauslaufen, wenn andere das nicht mitmachen.