Opened 11 years ago

Last modified 6 years ago

#675 new Bug/Something is broken

hard-error messages in the members' control panel should refer to specific and reference-able event id

Reported by: https://id.mayfirst.org/dkg Owned by: https://id.mayfirst.org/jamie
Priority: Low Component: Tech
Keywords: red-usability members.mayfirst.org f2f Cc:
Sensitive: no

Description

In #674, i discuss some disturbing results that i've stumbled into with red. For the mailing list in question, i'm now seeing a hard-error, and a message that looks like this:

You cannot modify a record that is pending other changes or has a status set to hard-error or deleted. Please wait until the status changes to make your change. If the status is set to hard-error please notify support.

This is problematic for two reasons:

  • hard-errors should automatically send notification to support in some form or other
  • even if there is an automatic notification, there should be an event ID of some sort generated, and the error message should include a link to this ticket system to automatically allow the user to create a ticket referring to this ID.

If we want people to report problems, we should make it really convenient for them to do so.

Change History (6)

comment:1 Changed 11 years ago by https://id.mayfirst.org/jamie

Good suggestions. I've been meaning to add the notification since I first started working red.

comment:2 Changed 6 years ago by https://id.mayfirst.org/dkg

I think this is related to #4445

comment:3 Changed 6 years ago by https://id.mayfirst.org/ross

  • Keywords red-usability added; red usability removed

comment:4 Changed 6 years ago by https://id.mayfirst.org/jamie

  • Priority changed from Medium to Low
  • Summary changed from hard-error messages in the members' control panel should automatically notify support to hard-error messages in the members' control panel should refer to specific and reference-able event id

I'm re-summarizing this ticket to focus exclusively on the event id reference suggestion because I think #4445 better describes the need around notification. And, I think each suggestion could be implemented in a self-contained way.

comment:5 Changed 6 years ago by https://id.mayfirst.org/jamie

Woops - not #4445 (which is about cleaning up existing errors). #5784 is the ticket that covers notification of support team about soft/hard errors.

comment:6 Changed 6 years ago by https://id.mayfirst.org/dkg

  • Keywords f2f added

we should try to work on this.

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.