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

Merge two notes/events into a single record #1414

Open
sleidig opened this issue Aug 31, 2022 · 2 comments
Open

Merge two notes/events into a single record #1414

sleidig opened this issue Aug 31, 2022 · 2 comments
Assignees
Labels
Type: Feature new user-facing feature

Comments

@sleidig
Copy link
Member

sleidig commented Aug 31, 2022

It may happen that two users record notes on the same issue. Or more commonly: there may be events (e.g. a workshop) where two groups have actually been participating together.
In this case users may afterwards want to combine the two entries into a single note/event that includes all participants and details of both merged records.

Proposed Solutions & Alternatives
The tasks and workflow could be like this (further discussion welcome):

  • add a way to select multiple rows in a table (i.e. multiple notes in the Notes List)
  • add a UI to perform actions on all the selected rows (this could also include "delete all", etc.)
  • add an action "merge selected", which will open the Note Details form filled with a combination of data of the records to be merged
  • if the user clicks "cancel", no merge happens; if the user clicks "save", the selected merged records are removed and the combined new one is saved

Merging two records should mean:

  • participants, groups and authors of the records are combined
  • details are kept if they are matching (e.g. interaction category, same title, ...)
  • details that are not matching are appended (e.g. note text or titles) or using the data of one of the records (e.g. interaction category); the form should visually highlight these fields so that the user can review and correct that
@sleidig sleidig added the Type: Feature new user-facing feature label Aug 31, 2022
@sleidig sleidig moved this to Triage in All Tasks & Issues Sep 5, 2022
@sleidig sleidig moved this from Triage to Todo in All Tasks & Issues Sep 5, 2022
@sleidig sleidig moved this from Todo (ready for work) to Triage / Analysis in All Tasks & Issues Feb 13, 2024
@sleidig sleidig mentioned this issue Sep 6, 2024
2 tasks
@sleidig sleidig moved this from Todo (ready for work) to In Progress in All Tasks & Issues Jan 21, 2025
@sleidig sleidig moved this from In Progress to Functional Review in All Tasks & Issues Jan 30, 2025
@sleidig sleidig moved this from Functional Review to In Progress in All Tasks & Issues Jan 30, 2025
@george-neha george-neha moved this from In Progress to Functional Review in All Tasks & Issues Feb 17, 2025
@george-neha george-neha moved this to Idea in Feature Roadmap Feb 18, 2025
@sleidig
Copy link
Member Author

sleidig commented Feb 18, 2025

Thanks for working out details of this feature and creating the sub-issues, @george-neha !
Could you please also paste screenshots of your early draft mocks. This will be very useful to discuss and inform the next level of detail for the implementation, in the respective sub-issue 🙂

Let's refine the first sub-issue #2855 first, until different developers do not have any open questions remaining when reading this.

@sleidig sleidig moved this from Functional Review to In Progress in All Tasks & Issues Feb 18, 2025
@sleidig sleidig moved this from In Progress to Waiting for External in All Tasks & Issues Feb 26, 2025
@sleidig
Copy link
Member Author

sleidig commented Mar 6, 2025

ideally, the headers (title "Merge Preview" column etc.) in the merge dialog would stay visible fixed, rather than scrolling out?

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature new user-facing feature
Projects
Status: Waiting for External
Status: Idea
Development

No branches or pull requests

2 participants