UX improvements to the codeflow page regarding subscription outcomes

[dkurepa]

After we rolled out #6334 we started getting some feedback:

• The failed subscription outcome list is a bit confusing right now as it does not mention that this is the last outcome. We should improve clarity there.

[dkurepa]

My personal UX improvement is that it might be nice to add the icon with this information to every row

where hovering this would show you the latest outcome, whatever it is. I'd also add date to there too, even for the failed ones as it appears to be something people care about

[adamzip]

Recent QBs thought it might be useful to have a date there too

That sounds like a good idea. Maybe it can just be made to match the columns of the actual outcomes page, because adding the date means the only thing missing would be the Outcome type, and it could probably be useful to include it too to show whether it's a server error or user error

[dkurepa]

The banner already separates user and server errors.

So if you want, we could remove this information from the banner and add it in rows. Maybe group errors together

[adamzip]

Oh I forgot about the two tables, that's fine then no need to change it

[dkurepa]

My personal UX improvement is that it might be nice to add the icon with this information to every row

where hovering this would show you the latest outcome, whatever it is. I'd also add date to there too, even for the failed ones as it appears to be something people care about

we decided we don't want this

[dkurepa]

Instead what we'd like to display is the need to resolve a conflict (or any other action triggering a merge policy failure)

[dkurepa]

I think maybe we should remove the distinction between user and service errors on this page for now, since we probably won't be doing user errors soon as it's a lower priority thing

[adamzip]

I think maybe we should remove the distinction between user and service errors on this page for now, since we probably won't be doing user errors soon as it's a lower priority thing

Ok, will merge them into a single table and add a Outcome Type column as part of this issue