Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No link to the ticket in an automatic response after submitting a bug report #5908

Closed
p6rt opened this issue Dec 24, 2016 · 4 comments
Closed
Labels

Comments

@p6rt
Copy link

p6rt commented Dec 24, 2016

Migrated from rt.perl.org#130399 (status was 'open')

Searchable as RT130399$

@p6rt
Copy link
Author

p6rt commented Dec 24, 2016

From @AlexDaniel

When you submit a ticket by writing a message to rakudobug@​perl.org it sends a response with some information. This information includes the ticket id and instructions on how to write replies.

However, it does not mention that the ticket is accessible on https://rt.perl.org. I think it should, and this was proposed in one of the comments on https://perl6advent.wordpress.com/2016/12/23/day-23-everything-is-either-wrong-or-less-than-awesome/

Given that bug reports sent to perlbug-admin at perl.org do not seem to be publicly visible, I am creating this ticket to track our efforts to get it done.

@p6rt
Copy link
Author

p6rt commented Dec 27, 2016

From @jkeenan

On Sat, 24 Dec 2016 23​:05​:51 GMT, alex.jakimenko@​gmail.com wrote​:

When you submit a ticket by writing a message to rakudobug@​perl.org it
sends a response with some information. This information includes the
ticket id and instructions on how to write replies.

However, it does not mention that the ticket is accessible on
https://rt.perl.org. I think it should, and this was proposed in one
of the comments on https://perl6advent.wordpress.com/2016/12/23/day-
23-everything-is-either-wrong-or-less-than-awesome/

Given that bug reports sent to perlbug-admin at perl.org do not seem
to be publicly visible, I am creating this ticket to track our efforts
to get it done.

The admin bug queue is not publicly visible, but I know from experience that it is monitored and the monitors are responsive. Simply forwarding your message to that address should start the ball rollilng.

Thank you very much.

--
James E Keenan (jkeenan@​cpan.org)

@p6rt
Copy link
Author

p6rt commented Dec 27, 2016

The RT System itself - Status changed from 'new' to 'open'

@p6rt p6rt added the rt label Jan 5, 2020
@usev6
Copy link

usev6 commented Apr 4, 2021

Since RT is no longer used for Rakudo bugs, I'll close this issue. (Nowadays Rakudo bugs are tracked at https://github.com/rakudo/rakudo/issues.)

@usev6 usev6 closed this as completed Apr 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants