Skip to content
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

Alignment problem with the API Message log table #1782

Closed
smcmurtry opened this issue Feb 20, 2025 · 3 comments
Closed

Alignment problem with the API Message log table #1782

smcmurtry opened this issue Feb 20, 2025 · 3 comments
Assignees
Labels
Bug | Bogue Dev Task for implementation of a technical solution Documentation Low Priority | Faible priorité

Comments

@smcmurtry
Copy link
Collaborator

Describe the bug

The alignment of data in the API message log is bad. I believe this is a regression - the table did not used to look like this.

Bug Severity

See examples in the documentation

SEV-4 Low

To Reproduce

Steps to reproduce the behavior:

  1. Log in to Admin (staging or prod)
  2. On a service that has API sends, visit the API Integration page and scroll down to the Message log
  3. Observe that the alignment in this table is off

Expected behavior

Rows in the Message log table should take up the full table width, relative dates should be aligned with each other

Impact

Impact on Notify users:
Looks bad

Screenshots

Screenshot 2025-02-19 at 4.34.35 PM.png

@yaelberger-commits
Copy link
Collaborator

Hey team! Please add your planning poker estimate with Zenhub @andrewleith @jzbahrai @smcmurtry @whabanks

@smcmurtry smcmurtry self-assigned this Mar 10, 2025
@smcmurtry
Copy link
Collaborator Author

PR reviewed an approved by @whabanks: cds-snc/notification-admin#2105

@smcmurtry
Copy link
Collaborator Author

The fix is deployed to prod.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug | Bogue Dev Task for implementation of a technical solution Documentation Low Priority | Faible priorité
Projects
None yet
Development

No branches or pull requests

2 participants