You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At TUW, we recently got feedback that it's slightly confusing to users that the comments that are written alongside request actions (e.g. "accept with comment") are rendered as two separate units in request detail pages.
On first glance, that takes away from the fact that they're actually one thing.
Context
When looking a the request's timeline in the API, there are several types of events; the relevant ones here being a LogEventType and a CommentEventType.
The first one marks the "accept" action being performed, the second contains the comment that was sent off along with the action.
It seems like there is currently no link between the two timeline events, which makes it hard to correlate them and also to render them together.
Perhaps we could introduce an optional link (via ID?) in the payload for comment events that tie them to their corresponding log event (if one exists)?
This could make it relatively simple for the UI to render them together as a single unit.
Current rendering
Expected rendering (example)
The text was updated successfully, but these errors were encountered:
At TUW, we recently got feedback that it's slightly confusing to users that the comments that are written alongside request actions (e.g. "accept with comment") are rendered as two separate units in request detail pages.
On first glance, that takes away from the fact that they're actually one thing.
Context
When looking a the request's timeline in the API, there are several types of events; the relevant ones here being a
LogEventType
and aCommentEventType
.The first one marks the "accept" action being performed, the second contains the comment that was sent off along with the action.
It seems like there is currently no link between the two timeline events, which makes it hard to correlate them and also to render them together.
Perhaps we could introduce an optional link (via ID?) in the payload for comment events that tie them to their corresponding log event (if one exists)?
This could make it relatively simple for the UI to render them together as a single unit.
Current rendering
Expected rendering (example)
The text was updated successfully, but these errors were encountered: