- Status changed to Fixed
about 2 years ago 6:02pm 5 June 2023 - Status changed to Needs work
about 2 years ago 11:46am 6 June 2023 - πΊπΈUnited States greggles Denver, Colorado, USA
This got kinda fixed so that s.d.o matched the order on d.o so maybe we need a followup to re-adjust the order on s.d.o to match what this is?
- πΊπΈUnited States drumm NY, US
Sure, we can do that. Is the order on Drupal.org looking good now?
- πΊπΈUnited States greggles Denver, Colorado, USA
Not quite.
d.o:
Project
Version dropdown
Affected versions composer thing
Security risk score
Vulnerability
Description
Solution
Reported by
Fixed by
Coordinated bys.d.o:
(missing) project
(too high) vulnerability
(too low) version
security risk
reported by
fixed by
coordinated by
(too low) description
(too low) solution - πΊπΈUnited States drumm NY, US
I'll update the order on security.drupal.org to match Drupal.org.
- πΊπΈUnited States greggles Denver, Colorado, USA
That seems great. Thank you!
- πΊπΈUnited States drumm NY, US
The field order is adjusted, that needs to be exported, once reviewed. And the HTML version tab still needs reordering.
- πΊπΈUnited States greggles Denver, Colorado, USA
Oooh, I probably should have said the place where field order on s.d.o is really important is on the /html view, e.g. https://security.drupal.org/node/177243/html
- Status changed to Needs review
about 2 years ago 8:15pm 9 June 2023 - πΊπΈUnited States drumm NY, US
I believe the field orders should be in sync everywhere now.
- πΊπΈUnited States greggles Denver, Colorado, USA
Perfect, thank you!
- Status changed to Fixed
about 2 years ago 5:39pm 10 June 2023 Automatically closed - issue fixed for 2 weeks with no activity.