The problem, as Ivan pointed out, is that our issue tracker would be cluttered with open reports in which the issue is probably fixed, but we're waiting for the reporter to confirm that it's fixed.
-> cluttered with open reports: yes you are right, in this case, can you through Github, to close automatically tickets after "3 days" if no answer ? -> not true, my ticket has been closed before my "report". Instead, if you find that your issue was closed without being fixed, you should simply say so in a comment on that issue. You could simply say, "This is still happening. Please re-open." -> ok for me Whatever you do, don't create a new issue when you know it's a duplicate of the old one! That causes confusion and creates extra work, which takes time away from working on the actual problem. -> agree I don't want to bother the team. Just my two pences. Thx 2018-02-01 6:38 GMT+02:00 Andrew David Wong <[email protected]>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 2018-01-31 08:25, ThierryIT wrote: > > Le mardi 30 janvier 2018 10:05:57 UTC+2, Ivan Mitev a écrit : > >> On 01/30/18 09:36, ThierryIT wrote: > >>> Hi, > >>> > >>> Why are you closing a ticket before knowing if the modification you > have made, to correct the bug, is working ? I mean, why can't you wait for > the user to add the modification and see if it is working or not ? > >> > >> Once a dev or contributor provides a fix that he/she thinks solves an > >> issue there is usually no reason to keep the issue open, or else the > >> issue tracker would be cluttered with fixed but open issues waiting to > >> be confirmed/closed by their reporter. > > > > Do not agree at all with this ... > > If taking as example my ticket, what happen: > > > > 1) I open a ticket for a problem > > 2) The ticket is taken into account by the dev > > 3) Work on it, push the patch > > 4) close the ticket > > 5) I do the update as requested > > 6) result: not fully working > > 7) Cannot re-open my ticket, open a new ticket > > 8) The dev close my second ticket because it is duplicated ticket > > 9) re-open the first ticket > > > > And what about: > > > > 1) I open a ticket for a problem > > 2) The ticket is taken into account by the dev > > 3) Work on it, push the patch > > 4) Ask the user to update and give feedback > > 5) if working then close the ticket, if not then go ahead ... > > > > What do you think ? > > > > The problem, as Ivan pointed out, is that our issue tracker would be > cluttered with open reports in which the issue is probably fixed, but > we're waiting for the reporter to confirm that it's fixed. Many > reporters wouldn't respond at all. That would make our issue tracker > much less efficient for our developers, which would in turn make them > less efficient at fixing bugs and adding features. > > Instead, if you find that your issue was closed without being fixed, you > should simply say so in a comment on that issue. You could simply say, > "This is still happening. Please re-open." (However, it would be more > helpful if you could provide more detail than that. We understand that > it's not always possible, though.) > > Whatever you do, don't create a new issue when you know it's a duplicate > of the old one! That causes confusion and creates extra work, which > takes time away from working on the actual problem. > > >> > >>> As exemple: ticket #3501 is closed, but even if I have followed the > instruction, the problem is not solved, but the ticket is closed ... > >> Either you're now hitting a bug that has nothing to do with your > >> original issue or Marek thought he fixed the bug but made a mistake. If > >> it's the former simply open another issue. If it's the latter, I'd send > >> Marek a friendly email, or I would create a new issue pointing to the > >> wrongly solved older one. > >> > > Please don't send emails to individual developers or create issues you > know are duplicates! Both are distracting and actually make it harder > for them to help you with your problem. Instead, please just add a > comment on the existing closed issue, as I explained above. We'll > receive a notification when you do. > > I've updated the Reporting Bugs page to try to clarify all of this: > > https://www.qubes-os.org/doc/reporting-bugs/ > > >>> How to re-open it ? > >> > >> You can't, it looks like it's a github shortcoming. Had you taken 2 secs > >> to websearch it, you'd have found: > >> > >> https://stackoverflow.com/questions/21333654/how-to-re- > open-an-issue-in-github#21333938 > >> > >> first hit, no need to even click the link, the answer is at the top of > >> the search page: "you cannot re-open your own issues if a repo > >> collaborator closed them". > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > > -----BEGIN PGP SIGNATURE----- > > iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpymZoACgkQ203TvDlQ > MDDgIxAAjtzKW1QtkK6HtYR+XcFpVR+sWAsT0xWzhk6eyTi5ob1yersq74h2sgzt > sZthRjz5q5x4ylWYR/6kB4jWj+Dc1aQkhieWmNKdSbpiV7fcdk94wFJQz7QaLUbq > zYjoiG8ERKSO0pS1X1ts1rUIed0EavGC5jYcnjDD9bUSqniXMhXUsv4G7Pq07I34 > CSrtjd4eXBKzdQ4ky0if2XAQlQF0LpTaKjhNlMUTouOuzCcQZWAtm62/UE5VzZq6 > 5KKHoM9iviCjzjV3HHDvWyHbT21o75RMBf8UE3WrpZOSoQkKZDRSFZ59J8URQ6Vn > I1Q/FtAMHKCNvRr1NvspvCVglpQ7mJCh4Cf8ataCB4swIj7eUMM7GUaDE79jYIrI > y+SkRIO0b7Pd+tQHLocjx2v+lVlcKc4QQlOnCMm86hUKfrSg38KrNJrnVs4VKhsu > zds4tqD2Wx1PIQ0nUkuNg2uF1G9uV84vLop9cKN5w4bsU4/Wgm1E8Kn6mwhK0f35 > OGF35PkTmp/wC3hrQxv5DW26rKM/3ejQ9cy/2U01nqxHWH4rCmMVMwPYxCQvfSrD > hkDIPJ2ba6OaZuzWjocJ1wlDT0UHYlfcF0V+dkWGhZfruSSv/v5XaKi1RmWh64GC > aWVWqNh/pYbkfjspBWDjfMLz6sjEDXhfCFiyFtYMr/locQjw8wk= > =SGK5 > -----END PGP SIGNATURE----- > > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAAsu1zNZ1wEOFBbFUM4cKzOUvpon2ET%3DREGp93vpJuV%3DB0%2BBpA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
