We need to figure out how we deal with printer status changes. If a printer is broken and then goes missing, the date when it went missing is important and should be shown in the printer details.
Idea 1:
Allow several issues per printer.
Complicated to implement, but gives exactly one message in the printer history per issue.
Idea 2:
Allow only one issue per printer, but show all the updates as individual bars in the printer history.
Easier to implement, but potentially causes many updates to be shown. This does not need to be a bad thing.
from #102:
I have a suggestion how to deal with scenarios like with Printer 31: changing the status on the printer from broken to missing doesn't add a comment but creates a new issue. In that case we have two open issues for a printer: the printer is broken AND it is missing. They can then be resolved individually. We do need to make sure that resolving an issue checks for other open issues to update the status. -> I think I will create a new issue from this and we can discuss the details there.
We need to figure out how we deal with printer status changes. If a printer is broken and then goes missing, the date when it went missing is important and should be shown in the printer details. Idea 1: Allow several issues per printer. Complicated to implement, but gives exactly one message in the printer history per issue. Idea 2: Allow only one issue per printer, but show all the updates as individual bars in the printer history. Easier to implement, but potentially causes many updates to be shown. This does not need to be a bad thing.
from #102: