Ticket #920 (closed bug: fixed)

Opened 5 years ago

Last modified 3 years ago

parrotbug should provide more guidance when it finishes

Reported by: jgabr Owned by: jkeenan
Priority: normal Milestone:
Component: tools Version: 1.4.0
Severity: medium Keywords:
Cc: Coke, whiteknight, cotto Language:
Patch status: applied Platform: all

Description

When parrotbug is done asking you questions about the bug you've found, it leaves you with this rather uninformative prompt:

Action (display,edit,save,quit):

I think it should provide more details about what to do next. For example, if the user should save their bug report for use later as an attachment when filing a bug report at trac.parrot.org, then I think it should say so.

It would also be nice if it specified whether the text in the bug report file should be copy/pasted into the new bug report text field, or if it should instead be an attachment to the new bug report.

Change History

  Changed 3 years ago by jkeenan

  • status changed from new to assigned
  • cc Coke, whiteknight, cotto added
  • component changed from install to tools
  • owner set to jkeenan

In order to work on this ticket, I used parrotbug to create the text of a bug report. I then submitted the bug report in two different ways:

1. Composed an email to tickets at parrot dot org and provided the bug report file as an attachment to that email (TT #2141).

2. Composed an email to tickets at parrot dot org and pasted the contents of the bug report file into the body of the email (TT #2142).

Do we have a preference? If so, I will include our recommendation in the revised version of what parrotbug prints on STDOUT as part of responding to the OP's concerns.

Thank you very much.

kid51

  Changed 3 years ago by cotto

copy/pasting sounds like a little less work. +1 to that approach. Having parrotbug automatically automatically submit bug reports would be preferable, but that's a separate issue.

follow-up: ↓ 4   Changed 3 years ago by dukeleto

I think parrotbug would be orders of magnitude more useful if it had the option to send the bug report email to parrot-dev. I would use something like that almost every day.

If we make parrotbug useful to core devs, it will useful to others as well.

in reply to: ↑ 3   Changed 3 years ago by jkeenan

Replying to dukeleto:

I think parrotbug would be orders of magnitude more useful if it had the option to send the bug report email to parrot-dev.

I don't necessarily disagree with you, but that would expand the scope of this Trac ticket considerably. (See also TT #2108.) We can close this ticket and proceed incrementally to a better parrotbug if we can, for now, choose between alternatives 1 and 2 described above.

duke, do you have a preference between these?

Other people's preferences?

Thank you very much.

kid51

follow-up: ↓ 6   Changed 3 years ago by jkeenan

  • patch set to applied

More detailed description of final Action selections provided in commit ba03bd8278.

I will keep ticket open 3 days for comments or complaints.

Thank you very much.

kid51

in reply to: ↑ 5   Changed 3 years ago by jkeenan

  • status changed from assigned to closed
  • resolution set to fixed

Replying to jkeenan:

More detailed description of final Action selections provided in commit ba03bd8278. I will keep ticket open 3 days for comments or complaints.

Util++ caught one error in an error message, but otherwise there were no comments or complaints. Closing ticket.

Thank you very much.

kid51

Note: See TracTickets for help on using tickets.