Content
View differences
Updated by Aleix Suau over 5 years ago
### **Environment**:
OpenProject 11.0.1
Chrome
### **Steps to reproduce:**
1. Have a milestone that is due on the current day or is overdue.
### **Actual Behavior**
The date color is not adjusted (still shown in black) - probably because for milestones the start and finish date are identical.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/19610/content"></div></figure>
### **Expected Behavior**
Today's finish date (or both start and finish date) is shown in orange.
Overdue finish dates (or both start and finish date) are shown in red.
### Development Notes
* Works in dev but not in QA
* wp-view-highlighting.service.ts >> shouldHighlightInline returns false because the 'name' of the field is not in this.current.selectedAttributes
* this.current.selectedAttributes is managed in WpTableConfigurationHighlightingTab
* WpTableConfigurationHighlightingTab takes the selectedAttributes from WorkPackageViewHighlightingService (this.wpTableHighlight.current) that is set in WorkPackageViewHighlightingService.initialize(query)
* Problems:
* WpTableConfigurationHighlightingTab always shows all the Highlighted attribute(s) (status, date, priority) independently of the query.highlightedAttributes value. value.
* DisplayFieldRenderer.renderFieldValue assigns the 'date' name to the dueDate field (because there is an schema.mappedName) >>> WorkPackageViewHighlightingService.shouldHighlightInline checks if the name is equal to any of the query.highlightedAttributes ids (this.current.selectedAttributes) but the id is not 'date', it is 'dueDate'.
I don't know what is wrong, the schema that has a wrong mapped name or the implementation that has to handle date instead of 'dueDate'.
OpenProject 11.0.1
Chrome
### **Steps to reproduce:**
1. Have a milestone that is due on the current day or is overdue.
### **Actual Behavior**
The date color is not adjusted (still shown in black) - probably because for milestones the start and finish date are identical.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/19610/content"></div></figure>
### **Expected Behavior**
Today's finish date (or both start and finish date) is shown in orange.
Overdue finish dates (or both start and finish date) are shown in red.
### Development Notes
* Works in dev but not in QA
* wp-view-highlighting.service.ts >> shouldHighlightInline returns false because the 'name' of the field is not in this.current.selectedAttributes
* this.current.selectedAttributes is managed in WpTableConfigurationHighlightingTab
* WpTableConfigurationHighlightingTab takes the selectedAttributes from WorkPackageViewHighlightingService (this.wpTableHighlight.current) that is set in WorkPackageViewHighlightingService.initialize(query)
* Problems:
* WpTableConfigurationHighlightingTab always shows all the Highlighted attribute(s) (status, date, priority) independently of the query.highlightedAttributes value.
* DisplayFieldRenderer.renderFieldValue assigns the 'date' name to the dueDate field (because there is an schema.mappedName) >>> WorkPackageViewHighlightingService.shouldHighlightInline checks if the name is equal to any of the query.highlightedAttributes ids (this.current.selectedAttributes) but the id is not 'date', it is 'dueDate'.
I don't know what is wrong, the schema that has a wrong mapped name or the implementation that has to handle date instead of 'dueDate'.