Closed Bug 1507233 Opened 7 years ago Closed 7 years ago

Provide more help and/or link to FAQ regarding backouts in improper-author-info error

Categories

(Conduit :: Lando, enhancement, P1)

Production
enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mcote, Assigned: imadueme)

Details

(Keywords: conduit-triaged)

Attachments

(2 files)

Because of bug 1489126, many people are getting the improper-autho-info error: "Diff does not have proper author information in Phabricator. This can happen if the diff was reated using the web UI, or a non standard client." Since a frequent source of these errors is from relanding attempts after Phabricator has clobbered the author info, we should provide more help here, until the underlying problem is solved.
This is an easy improvement.
Keywords: conduit-triaged
Priority: -- → P1
This blocker is present on https://lando.devsvcdev.mozaws.net/D474/. You can hover over the 'Blocked' icon to see the message. Can you check that out and determine what the best way to add a longer message/FAQ link is? (Do you want to just tack on FAQ to the end of that blocker message?) The UI is not ideal for long error messages.
Flags: needinfo?(mcote)
The sentence "This can happen if the diff was created using the web UI, or a non standard client." doesn't seem to provide much value on its own (people have been confused by it regardless of the cause). How about just replacing it with "Please see this FAQ entry."?
Flags: needinfo?(mcote)
The text in the no author information error message was not really helpful on it's own; it would need to be much longer to actually guide the user in fixing the problem. Instead of trying to summarize things, we simply direct the user to the FAQ and the UI will be able to link out to the FAQ.
The keyword was linked in the old non-stack UI but we forgot to do the same on the stack UI.
Assignee: nobody → imadueme
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: