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

  • 2 Posts
  • 329 Comments
Joined 2 years ago
cake
Cake day: June 29th, 2023

help-circle










  • It’s a western perspective. And of course it is. How many people of the sovjetbloc do you think are around here? I thought about this for a second and dismissed it because it’s with a 99% chance not relevant to the one asking here.

    But still, thank you for providing this perspective, it is like you say, I just didn’t think it was relevant to this question in this place we’re in.


  • hear about

    Something is only talked about if talking about it accomplishes something. Gen X doesn’t raise any strong feelings with anyone, so they’re not talked about. They’re still there obviously.

    The reason why is complex, and I’m no expert myself. However, from what I gathered about recent history, what seems most likely to me is that the time gen x’ers grew up in was very stable in the sense that economy was good, no major wars were happening, the cold war was “ending”. So the only thing gen x’ers had to worry about was themselves. So they did. And you don’t really need to talk about someone that just keeps to themself. They cause you no issues.

    Another theory of mine is very simple: humanity changes over time. The larger the time, the larger the change. Differences between humans breeds conflict as their interests collide. Since boomers are the current oldest larger impactful generation, and gen z are the youngest, the difference between them are greatest. Thus the conflict between them is highest, thus there are a lot of people talking about those problems. I’ve been hearing less about millennials as well.







  • 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.