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

Library Certificates list does not include environments on subsequent "load more" pages #4924

Closed
thebigmoosey opened this issue Sep 27, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@thebigmoosey
Copy link

commented Sep 27, 2018

Library Certificates list does not properly map environments for subsequent page results

If you click "Load More" on the certificates list (and those certificates are scoped to environments), environments are not being shown in the list screen.

Our implementation does not take into consideration the potential subsequent pages of results. We have a pattern to address this in our paging component, so this pattern has not been used correctly here.

Steps to reproduce

  1. Go to 'Library > Certificates'
  2. Add more than 100 certificates scoped to environments
  3. Scroll to the bottom and click "Load More" to get the next page of results
  4. See that next page of certificates is missing environment information

Affected versions

v4 and above.

Workarounds

There are no workarounds for this issue currently, other than clicking into each record to see the environment.

Source

https://help.octopus.com/t/bug-library-certificates-after-paging-the-environment-is-gone-in-the-list/21409

@fsettele

This comment has been minimized.

Copy link

commented Sep 28, 2018

Asome - thanks for your quick replay!

@shaunmarx shaunmarx self-assigned this Oct 3, 2018

@shaunmarx shaunmarx closed this Oct 4, 2018

@octoreleasebot octoreleasebot added this to the 2018.8.9 milestone Oct 4, 2018

@octoreleasebot

This comment has been minimized.

Copy link

commented Oct 4, 2018

Release Note: UI fix for Library Certificates paging issue

@lock

This comment has been minimized.

Copy link

commented Jan 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 2, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.