Skip to content
This repository has been archived by the owner on Jun 12, 2024. It is now read-only.

Change maintenance dialog field order #909

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Spreadcat
Copy link
Contributor

What type of PR is this?

  • enhancement

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 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.

Adding the currency of norwegian krones back into the file. There was an earlier commit where this seems to have dropped of the table.
When using the maintenance dialog, the order
title/scheduled/completed/costs/notes seems to be  more sensible than
title/completed/scheduled/notes/costs.
Though notes/costs vs. costs/notes certainly can be argued about, in
most of my cases this order would be more useful than the other way
around.
@Spreadcat
Copy link
Contributor Author

Not sure why these checks fail. It looks to me like something is wrong with the CICD infrastructure.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant