Postgres decided out of the blue to shake up how it returns ordering for Stages inside a project. Normally it follows per the creation date of rows but for some reason decided not to today. We're taking steps to reduce the risk on our system.
What does this PR do?
Related JIRA tickets:
Did the user.integration, discussion.integration and task.integration tests pass? Test can be run with:
Create or use an existing project that has several stages, preferably up to 5 or 6. (You are capped at 4 when using the Project Wizard, but can go beyond this limit on the Project Management page). Confirm that they appear in order. Then go into your backend and try switching the order at the WorkflowSteps table. See the screenshot for how. You may want to put your order back when you are finished.
Also, please check that the Projects page for admin users lists and confirm that it is now ordered from latest to last updated.
Postgres decided out of the blue to shake up how it returns ordering for Stages inside a project. Normally it follows per the creation date of rows but for some reason decided not to today. We're taking steps to reduce the risk on our system.
What does this PR do?
Related JIRA tickets:
Did the user.integration, discussion.integration and task.integration tests pass? Test can be run with:
node_modules/.bin/mocha test/user.integration.js test/discussion.integration.js test/task.integration.js --bail -t 10000
How should this be manually tested?
Create or use an existing project that has several stages, preferably up to 5 or 6. (You are capped at 4 when using the Project Wizard, but can go beyond this limit on the Project Management page). Confirm that they appear in order. Then go into your backend and try switching the order at the
WorkflowStepstable. See the screenshot for how. You may want to put your order back when you are finished.Also, please check that the
Projectspage for admin users lists and confirm that it is now ordered from latest to last updated.Background/Context
Screenshots (if appropriate):