+1 to a simple link that fills in most of the fields in JIRA, though this doesn't solve the issue of having to sign up just to submit a bug report. Just using the users list isn't a bad idea either--we could easily create a script that ensures all threads that have a message like "we should file a JIRA for this" are followed up with a message like "JIRA filed at ...". (That doesn't mean it won't language on the tracker.)
I think it's worth seriously considering just using Github's issue tracker, since that's where our users are. Is there anything in we actually use in JIRA that'd be missing? On Wed, Jul 29, 2020 at 10:30 AM Kenneth Knowles <[email protected]> wrote: > Very good points. We want the barrier to filing a bug report to be as low > as possible. Jira adds complexity of a sign up process and a complex > interface, and also users don't know what the fields mean (issue type, > priority, component, tag, fix version, etc). So it currently really doesn't > make sense to just point users at Jira and expect them to figure it out. > > As for using user@beam for bug reports: > > - In practice, we have to edit most of the fields and improve the bug > description anyhow, so it might be no extra work for an experienced > contributor to file the bug based on the user's email. > - Also in practice, we already do this. So it is just a matter of > pointing users that way. > > One downside is that there is not really tracking of resolution of an > email thread, so unless it gets filed as a Jira it may sit unresolved. > > Another option we could consider: I think we could have a "report a bug / > feature request" link that fills in most fields and gives the user a > simplified view (like GitHub issue view where it is just title & body). It > could end up that these Jiras get ignored just as easily as a user@beam > thread. > > You can always have a link like that and it could point to whatever the > current choice is, like "mailto:[email protected]"; though I think > mailto links are out of fashion these days. > > Kenn > > On Fri, Jul 24, 2020 at 2:50 PM Griselda Cuevas <[email protected]> wrote: > >> Hi folks, >> >> I recently made a few Jira boards [1][2] to help triage and organize >> Beam's backlog. >> >> >> Something that came to my mind is that reporting bugs and feature >> requests using Jira might be imposing a high barrier for users who don't >> have an account. This process might also make it difficult to ask follow-up >> questions to reporters who don't monitor Jira's notifications. >> >> >> I want to gather consensus on updating the website to give the option to >> report bugs and feature requests by sending an email to [email protected] and >> adding a tag to the subject line ([bug] OR [New Feature]) >> >> >> There are other more sustainable solutions, like looking into using >> GitHub issues, but they will have other costs, like migrating current >> tickets and systems, pointing them out here in case we want to consider. >> >> >> Let me know what you think, >> >> G >> >> >> [1] >> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335922# >> >> [2] >> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335923# >> >> [3] https://beam.apache.org/contribute/ >> >> [4] https://beam.apache.org/community/contact-us/ >> >
