fusionauth-issues
fusionauth-issues copied to clipboard
UI Updates for webhook event log
UI Updates for webhook event log
Description
Some things we should update to make this new UI feature more consistent.
- On the index page we should use the event type
user.createinstead ofUser Create. See the event table on Webhooks. Ideally we'd the event type and event description if there is room. - On the attempt view dialog, I think
Exceptionshould come afterResult. - We may want to collapse the Webhook URL and Id into one field with multiple rows. This is a pattern we have in various other locations for email templates, or the like.
- In the view dialog, use the same duration syntax as the attempt table. For example, use
22 msinstead ofDuration (ms): 22. Ensure this value is formatted in case it exceeds1000so that it will be displayed as1,000. - On the attempt index page, instead of
startandendcolumns should we have asentand a duration? And leave thestart / endto the view dialog? This may be more meaningful. - Review the mobile size of the webhook event log, I think we are squishing columns.
- Add the new action menus to these new pages.
- On the index page where we have the details of the event on top, show both the event type as
user.createandUser Create. - Review copy for
Linked object Id. - Review index page for webhook log for the
Attemptscolumn, can we simplify this to not have the parens forsucceeded/total, this could move to a tool tip or we could re-word the column to be more descriptive without the parens. - In the advanced search, change the order of the
Event resultdrop down to beCompleted,In ProgressandFailed - Review the advanced search, does
endmake any sense here` What is "end"? I think we are really searching between two bounds of when an event was created? Review this copy. - General review of the view dialog for consistency with the rest of the panels.
Related
- https://github.com/FusionAuth/fusionauth-issues/issues/2874
- https://github.com/FusionAuth/fusionauth-issues/issues/2901
Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.