Skip to content

Handle moderation status mismatch when conflict occurs while filtering by another status #9802

@acelaya

Description

@acelaya

When moderating an annotation, the next situation can happen (from this comment):

  1. Visit the moderation queue in two separate tabs and filter by PENDING
  2. In first tab, change status to APPROVED
  3. In second tab, change status to DECLINED.

In the second tab, a conflict will be detected and the annotation will be reloaded. It will now show the APPROVED status that was set in tab (2), even though the list is filtered by PENDING.

If it was enforced that the list and filter stay in sync, the annotation would have to disappear since it moved to the APPROVED view. That would be even more confusing, plus we'd need to display a new notice telling them what happened.

We need to decide what should actually happen. For consistency, the annotation should eventually be removed from the list, but perhaps we could "move" it to a secondary "floating" list of annotations that no longer match current filter but you are interacting with.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions