Filter by update conflicts in Entity table

[matthew-white]

See the story in the release criteria.

Frontend PR: getodk/central-frontend#874
Backend PR: getodk/central-backend#1024

[matthew-white]

Things that Backend will need to do:

• Return a __system/conflict property over OData.
• Filter entities on that property.
• Support $filter for CSV downloads. Filter entities CSV download #521

[issa-tseng]

looks good. it would be nice someday if when it's "1 of x" in the filter dropdown just show the selected option (truncated if too long).

[matthew-white]

That's definitely doable (and configurable per filter). In this case, "Possible conflict" is relatively long, and if we make the filter wide enough for it, there will be a fair amount of unused space in the "2 of 2" case. Is that OK?

On the submissions page, I don't think we'd want to make those filters any wider, since there's a lot going on in that row. I could still make the submitter filter and the review state filter show the one selected option, but it'd often be truncated.

[dbemke]

The expected design for the conflict status filtering is this?

not the one from release criteria ( different text in the conflict status field + show columns filter)?

[matthew-white]

@dbemke, yes, that's currently expected. "Conflict status" will be shown below the filter, not within it. We also haven't added a column selection dropdown yet (and won't as part of this release).

[dbemke]

Tested with success!

[srujner]

Tested with success!