-
Notifications
You must be signed in to change notification settings - Fork 385
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
Improved “single error” by URL view #1365
Comments
@jwold @jillchu - I'd also like your thoughts on how to surface @kienstra's comment here to benefit this ticket as it hasn't been discussed yet and we shouldn't lose this feature in the new version of single error views. |
As discussed in today's backlog grooming call, this screen's intention is to
|
In Progress I'm working on this (1365) now, on this branch. |
Question About Latest Designs Hi @postphotos, Thanks 😄 |
Hi @kienstra - yes, and I've updated the story! Missed this ticket. 🥇 |
Sure, @postphotos! |
Request For Testing Hi @csossi, Please use this staging site, as it has the latest corrections from PR #1462. And please see this screencast for the expected functionality of this page. |
Verified in QA Assumption here is that tooltip positioning is a separate issue logged elsewhere |
As a developer using the AMP for WordPress plugin, I should have improved organization of errors that occur by error type.
AC1: Implement the new design linked below. This sunsets the "accordion" layout and introduces a "table" layout for single URL error listings.
AC2: Incorporate facets by "Error Type" so that a developer could see just errors by Javascript for a given single URL, for example.
AC3: Also Incorporate search to manipulate which errors are shown in the table listing. Search would appear above the table.
AC4: Allow for bulk actions to accept, reject and delete errors on a per-error basis.
AC5: Continue to provide a full stack trace information/error dump in the form of a collapsible blob, as shown on the mockups and currently implemented as of
v1.0-beta2
.AC6: Provide extended "status" information
Based on the new screen described
here here hereFinal Designs: [ Page 1 ] [ Page 2 ], additional actions and an improved UI will allow a developer to better understand what errors occur on a per-URL basis and how to quickly action to suppress errors if they choose to do so.The UI includes organizing the error blocks and provides a link to the appropriate place for the given user to understand how to best action to resolve the error long term, likely using the taxonomic data from #1360 to connect to relevant pages from amproject.org or ampbyexample.com or our documentation.
The text was updated successfully, but these errors were encountered: