This PR changes the order of the fields in the maintenance dialog. The original order was
title/completed/scheduled/notes/costs.
This changed to title/scheduled/completed/costs/notes.
When using the maintenance dialog the scheduled information was always earlier available than when the maintenance was completed. Therefore that field coming right after the title seems to be more sensible.
Something similar was/is true for the order of costs and notes. In my use cases I have more often a value for cost than actually for notes, which is why it seems more meaningful to have the field coming before notes. Also notes is the bigger field, which layout wise makes it slightly more sensible to put to the end. That way Costs does not get completely out of focus.
Which issue(s) this PR fixes:
None
Testing
created a docker image, fired it up and verified the position of the fields has changed accordingly.
Release Notes
Changing the order of the fields in the maintenance dialog of an asset.
What type of PR is this?
What this PR does / why we need it:
This PR changes the order of the fields in the maintenance dialog. The original order was
title/completed/scheduled/notes/costs
.This changed to
title/scheduled/completed/costs/notes
. When using the maintenance dialog the scheduled information was always earlier available than when the maintenance was completed. Therefore that field coming right after the title seems to be more sensible.Something similar was/is true for the order of costs and notes. In my use cases I have more often a value for
cost
than actually fornotes
, which is why it seems more meaningful to have the field coming beforenotes
. Alsonotes
is the bigger field, which layout wise makes it slightly more sensible to put to the end. That wayCosts
does not get completely out of focus.Which issue(s) this PR fixes:
None
Testing
Release Notes