Status in Html-Field (Solution Status)

[wojosc]

A common Problem is that you do not see if there also problems with certain Solutions when working on a single issue. To know this you would have to know or search. The later can be very time consuming though...

I suggest we have a status section which will pull the decription and Status (with indicator) from all solutions which are linked to items which are listed in IT Management Table.

[majubewi]

• [x] Huge progress.
• [x] Find out how ERPNext/frappe does the backwards search in general or in special in chiltables... find the frappe method and try to use it.
• [ ] If not possible use SQL by going through all childtables of the system... or fuzzy other way.

[majubewi]

Thema soweit beendet.

Ohne einheitliche Statidefinitionen ist ein Solution Status oder ein Status in der IT Management Table nicht möglich.

# In allen doctypes auf dem Solution dashboard das feld Status vereinheitlichen.
# Für jedes dieser Statusfelder ein Farbmapping erstellen. Doppelte Belegung möglich
# 

Beispiel: # ----------------------------------------------------------- # - Stati - Farbe - # ----------------------------------------------------------- # - Implementing - orange - # - Running - green - # - Issue - red - # - Obsolet - grey - # -----------------------------------------------------------

[majubewi]

Branch: status_lab

Example Status:

Config Item (color) - Solution implementing (red) - (red) running(green) - (green) warning(orange) - (orange) stopped(red) - (red) obsolet(grey) - (gray)

Rules:

• If min one item is red => Solution is red
• Ignore items obsolet
• If min one item is orange and no item is red => Solution is orange
• If all items obsolet => Solution is grey
• Else => Solution is green

Notiz für Berechnung anderer möglicher Solution Stati: Berechnung des Solution Status: Farbe zu Ganzzahl mappen, dann:

• Durchschnitt (gerundet)
• Durchschnitt (mit Grenzwerten)
• Regelbasiert (z.B. ein "rotes" Item => Solution Status == "rot")
• Median (gerundet)