A few of fields for editing on https://www.drupal.org/node/add/sa are in a different order than when they are displayed, e.g. on https://www.drupal.org/sa-contrib-2019-004
Specifically
* Adding/editing the "Description" and "Solution" fields come at the end of the list (after Reported by, Fixed by, Coordinated by)
* When viewing, Reported by, Fixed by, Coordinated by come before the "Description" and "Solution" fields
* The order of the fields in viewing is the same as they are presented on s.d.o
It would be easier to copy and paste the advisory from s.d.o to d.o if the fields were in the same order when editing (with Description and Solution before Reported by).
Comments
Comment #2
drummComment #3
drummComment #5
drummComment #6
gregglesThis 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?
Comment #7
drummSure, we can do that. Is the order on Drupal.org looking good now?
Comment #8
gregglesNot quite.
d.o:
Project
Version dropdown
Affected versions composer thing
Security risk score
Vulnerability
Description
Solution
Reported by
Fixed by
Coordinated by
s.d.o:
(missing) project
(too high) vulnerability
(too low) version
security risk
reported by
fixed by
coordinated by
(too low) description
(too low) solution
Comment #9
drummI'll update the order on security.drupal.org to match Drupal.org.
Comment #10
gregglesThat seems great. Thank you!
Comment #11
drummThe field order is adjusted, that needs to be exported, once reviewed. And the HTML version tab still needs reordering.
Comment #12
gregglesOooh, 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
Comment #14
drummI believe the field orders should be in sync everywhere now.
Comment #15
gregglesPerfect, thank you!
Comment #16
drumm