NMRL-171 Priority not showing on Analysis Request listing #230
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Priorities as an ATContentType were removed some time ago because of performance leaks. With this Pull Request, Priority field is reintroduced for Analysis Requests, but as an StringField populated with a pre-defined set of priorities: Lowest, Low, Medium, High, Highest. The default priority is "Medium".
The Priority field is displayed as the first column in lists and is sortable in such a way that when sorted ASC and 2 analysis requests have the same priority, but they were created at different dates, the oldest appears first. When sorted DESC, items with lowest priority are displayed first and, by following the same rule, newer are displayed first.
Screenshots
Priority column in Analysis Requests (not sorted, by default):
Priority column in Analysis Requests (sorted ASC):
Priority field in Analysis Request's Edit view:
Priority field in Analysis Request's Add view: