chealer

chealer_issues.md

You were banned from posting to debian-release at the request of the release team. After sending the same mail now sent to the BTS to listmaster both Don and I told you that this is on purpose and not a bug. This remains to be the case.

This obviously makes this ITS hardly usable. As GitHub's issue tracking system engine has been dormant for a long time, I recommend to switch to a proper engine. The only one I know enough to recommend is Atlassian Jira.

igorescobar, I do not need to convince anyone that this is worth implementing to keep this ticket open. It is whoever wants to close this who needs to explain why this would be invalid.

dmethvin, why did you close this ticket?

Timmy, I asked Dave in ticket #148 why he closed the ticket and no one has replied since.

dmethvin, why did you close this ticket?

Thank you @jakeNiemiec. I looked at a random ticket, #4740 and while I won't comment on intentions, I fully agree with @jonahgreenthal about this being unaccceptable. - this is a good one.

Either the "Issues" tab should be renamed something like "Issues & Questions", or questions should be split to somewhere else (I would favor that avenue).

I'm afraid this persists, even in DBeaver 7.2.1. Why is this ticket closed?

Why is this ticket closed?

Closing a ticket means that the reported issue is solved; it does not merely express that someone chose not to fix it.

generally not getting it

This conversation has been locked and limited to collaborators...There is no explanation for why that happened

Why is this report closed?

"Is there a reason this ticket is closed?" - "Because we are not Github and we use the issue tracking system Github provides"

Thanks @stephen-turner but closed tickets are not those about upstream issues. Tickets are closed when the issues they track are resolved.

Thanks, but issues are closed when they are solved. It is OK not to intend to solve all issues, you can just leave the tickets as they are.

Why is this ticket closed?

@docker-desktop-robot why was this ticket closed?

@easyphp why did you close this ticket?

"I'm not sure what a PR is," - last month.

Doesn't like github issues

This false negative is in fact caused by a default search criteria which can be seen in the input field's default value: is:issue is:open "is:open" excludes closed tickets.

I don't know what you mean by "team's backlog tracking", but this is certainly not expected. When we see a ticket template called Bug report, the expectation is that it allows reporting any bug.

Thanks @lorenrh but a ticket is not closed just because a developer does not intend to work on it.

The Features page of Stretchly's website covers features, but also contains considerable offtopic content, including at least the Contributors, Humans and Tools and License sections.

While Angular's ITS tracks lots of issues, unfortunately, the project is way too large to efficiently analyze even a small representative sample of its tens of thousands of issues. ..By far the best solution would start by migrating to a proper ITS engine. Most importantly, mature engines provide:

---

as Philippe Cloutier

I do not see why legal issues should be discussed privately,

"It is a request for a change that has been considered and declined." "None of that resolves the problem."

Justin, all issues are associated with a desire for a change, whether they are bugs or not. Importance wishlist is reserved to tickets which do not report defects.

just never ending questions and suggestions of work

For god sake, could you send a patch with proposed changes next time instead of filling bug reports for such minor stuff?

Doesn't like version number in title

Please do not close reports without justification.

I fail to see why this is tagged wontfix.

"You're expected to read the entire thing when refered to a bug report in a thread you're replying to." "I was unaware of that."

Thinks that because he doesn't understand a bug tool, it must be broken

misreads something and wastes time

winding people up

> In case it was not obvious to you, you managed to annoy a lot of people > with your behaviour (even if you did not do it on purpose) and it might be > a good idea to keep a low profile to avoid further problems.

---

Filipus Klutiero

cmderdev/cmder#2401 (comment) cmderdev/cmder#2400 (comment) dbeaver/dbeaver#7270 https://github.com/easyphp/easyphp-devserver/issues/120#issuecomment-886222449

microsoft/vscode#127714 (comment) pbek/QOwnNotes#1403 spring-projects/spring-boot#23545 (comment) whatwg/html#4835

Blocked on wikipedia - bonus drama

Blocked in spring-projects as well, see spring-projects/spring-framework#28854