Inconsistent commands for multi-word statuses in email

Bug #392132 reported by John A Meinel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Undecided
Unassigned

Bug Description

The code review email commands are similar to, but diverge slightly from the ones for bug reports.

Specifically, I believe the request is:

  vote needs_fixing
  (although 'needsfixing' and 'needs-fixing' also work -- jml)

but for bugs it is

  status fixreleased

Since email is sort of "fire-off-and-hope-you-got-the-syntax-right" it is probably best to accept more possibilites.

Anyway, I always get screwed over by stuff like vote and status because they are multi-word entries but doing:
  status fix released

gives errors about it only accepting 1 argument.

It would at least be nice if the method of turning 2 words into 1 argument was consistent across the different email interfaces.

Tags: email lp-bugs
John A Meinel (jameinel)
tags: added: code-review
Jonathan Lange (jml)
tags: added: email
Revision history for this message
Jonathan Lange (jml) wrote :

 vote needs-fixing
 vote needsfixing
 vote needs_fixing

All work, and all do the same thing. Although this doesn't match bugs exactly, I wouldn't have thought that the extra permissiveness caused confusion.

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 392132] Re: code review email interface inconsistent naming structure

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jonathan Lange wrote:
> vote needs-fixing
> vote needsfixing
> vote needs_fixing
>
> All work, and all do the same thing. Although this doesn't match bugs
> exactly, I wouldn't have thought that the extra permissiveness caused
> confusion.
>

I find the email interfaces difficult in general, because it requires me
to internalize a random syntax. Not terrible, but certainly not as
obvious as a drop-down list.

Anyway, somehow I discovered that "needs_fixing" works, and so started
using it. Then I went to update a bug, and found that "fix_released"
does *not* work.

I would probably prefer more flexibility, but the fact that the bug
emails *don't* support it is confusing.

(I originally thought that it was "vote needs_fixing" always and "status
fixreleased" always, which was the original point of this bug.)

Also, email interfaces aren't really something that I want to fire off
several emails to see which thing really works...

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpEN4gACgkQJdeBCYSNAAOGoQCg1xc3PNzIdRetj4WZ1AOStR3X
YAUAoK3mPjy8eSMLbqWeP/GJ0k4taQn7
=yl1J
-----END PGP SIGNATURE-----

Revision history for this message
Jonathan Lange (jml) wrote : Re: code review email interface inconsistent naming structure

In that case, I reckon I'll re-assign the bug to malone and tweak the description a bit.

affects: launchpad-code → malone
Changed in malone:
status: New → Triaged
tags: removed: code-review
summary: - code review email interface inconsistent naming structure
+ Inconsistent commands for multi-word statuses in email
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.