Thanks for the input folks, I'm reading your contributions, I will look into
proposing a solution summarizing the conversation at the end of the week, so if
you have other ideas share them here.
Thanks!
On 2020/08/04 18:42:15, Alex Amato wrote:
> May I suggest we print a URL(and a message)
May I suggest we print a URL(and a message) you can use to file bugs at, in
the command line when you run a beam pipeline. (And in any other user
interface we use for beam, some of the runner specific UIs may want to link
to this as well).
On Tue, Aug 4, 2020 at 9:16 AM Alexey Romanenko
wrote:
Great topic, thanks Griselda for raising this question.
I’d prefer to keep Jira as the only one main issue tracker and use other
suggested ways, like emails, Git issues, web form or dedicated Slack channel,
as different interfaces designed to simplify a way how users can submit an
issue. But
I do like the idea of the "mwrong way to raise issues point to the correct
ways.
On Fri, Jul 31, 2020, 10:57 AM Brian Hulette wrote:
> I think I'd prefer continuing to use jira, but GitHub issues are certainly
> much more discoverable for our users. The Arrow project uses GitHub issues
> as a
I think I'd prefer continuing to use jira, but GitHub issues are certainly
much more discoverable for our users. The Arrow project uses GitHub issues
as a way to funnel users to the mailing lists and JIRA. When users go to
file an issue they're first given two options [1]:
- Ask a question ->
On Wed, Jul 29, 2020 at 7:12 PM Kenneth Knowles wrote:
>
> On Wed, Jul 29, 2020 at 11:08 AM Robert Bradshaw
> wrote:
>
>> +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
On Thu, Jul 30, 2020 at 6:37 AM Maximilian Michels wrote:
> +1 for making it easier to report bug. Very often we have users report a
> bug and then they have to rely on a developer to report the issue
> because they don't want to bother creating a JIRA account (which is
> understandable). If you
+1 for making it easier to report bug. Very often we have users report a
bug and then they have to rely on a developer to report the issue
because they don't want to bother creating a JIRA account (which is
understandable). If you have a JIRA account it is easy because you don't
need any
On Wed, Jul 29, 2020 at 11:08 AM Robert Bradshaw
wrote:
> +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
+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
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
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
12 matches
Mail list logo
