Uninett
Redesign the details dialog
..., but it reminds me again that we really should look at redesigning the details dialog...
Originally posted by @lunkwill42 in https://github.com/Uninett/Argus-frontend/pull/557#pullrequestreview-2003111045
After the CLOSE/REOPEN button in the new frontend is moved from the details dialog, I personally am satisfied with the design and for my part this issue can be closed. What did you have in mind with redesign @lunkwill42? The new design, for context:
What did you have in mind with redesign @lunkwill42?
To be honest, I didn't author this issue, and I've had no input on it. @hmpf made it based on a comment I gave in a review.
When I refer to the "details dialog", I am referring to more than just the details column of the dialog, of which you attached a screenshot. AFAIK, the new design replicates the old front-end in that there are three columns of information in the dialog. The reason I made those comments originally is that I am constantly left with a feeling that these columns are very unbalanced in how much information they carry.
The left column carries a wealth of information, but its size is normally quite fixed (except for the tag balloons you left out of the screenshot, these can be few or however many a user wants to inject into an incident).
The middle column carries acknowledgements. There is rarely more than a single acknowledgement attached to an incident. Sometimes, maybe two.
The third column can grow indefinitely, depending on the source system, since it is basically a log of events that concern the incident (minus acknowledgement events, which have their separate column, to make them stand out). Many incidents will maybe have just 1 open and 1 close-event here. Others can come to contain several pages of events.
I don't always feel competent in UX (I prefer the back-end, as you know), so I'm not sure I have concrete suggestions for improvements. I guess my thinking here is that we should explore alternative designs for the dialog as a whole. We're scheduled for an initial meet with some in-house UX experts next week, and I'm thinking this is an idea we can throw their way to see what they make of it.
(In other words, I think we should transfer this issue to the Argus repo, since my misgivings about the dialog design carries over to the new UI as well)
