Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add first version of entity conflict summary box #530

Closed
matthew-white opened this issue Oct 27, 2023 · 0 comments · Fixed by getodk/central-frontend#890
Closed

Add first version of entity conflict summary box #530

matthew-white opened this issue Oct 27, 2023 · 0 comments · Fixed by getodk/central-frontend#890
Assignees
Labels
entities Multiple Encounter workflows frontend Requires a change to the UI

Comments

@matthew-white
Copy link
Member

#505 calls for a summary box about entity update conflicts. The summary box has a few component parts:

  1. Summary table (to be done in Add entity conflict summary table #529)
  2. "Mark as resolved" button and the footer that contains it (to be done in Mark update conflicts as resolved on Entity Detail page #506)
  3. Lastly, the header at the top of the box

This issue is to add a first version of the summary box to the entity detail page. For this issue, the box should start out with just the header.

@matthew-white matthew-white added frontend Requires a change to the UI entities Multiple Encounter workflows labels Oct 27, 2023
@github-project-automation github-project-automation bot moved this to 🕒 backlog in ODK Central Oct 27, 2023
@sadiqkhoja sadiqkhoja self-assigned this Nov 2, 2023
@sadiqkhoja sadiqkhoja moved this from 🕒 backlog to ✏️ in progress in ODK Central Nov 2, 2023
@github-project-automation github-project-automation bot moved this from ✏️ in progress to ✅ done in ODK Central Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
entities Multiple Encounter workflows frontend Requires a change to the UI
Projects
Status: ✅ done
Development

Successfully merging a pull request may close this issue.

2 participants