"Merge Entries" in "multiwaymerge" doesn't work

[ZiadAbdElFatah]

Steps to reproduce the behaviour

1. Open example library
2. Choose an entry for example Garcia_2018
3. Lookup -> Update with bibliographic information via entry data

4. Choose any field that differs from the original entry for example ISSN

5. Click on Merge entries

The intended output is that the ISSN changes to the one chosen, and this doesn't happen.
Here is the ISSN field after merging:

[koppor]

Your screenshots show that the "Merged entry" contains the new data. - Then follow the control flow where this BibEntry is "sent" to / how it is handled. You can also draw a UML sequence diagram.

[ZiadAbdElFatah]

I think the correct workflow is when clicking on Merge entries, the Original entry gets updated to the fields in the Merged Entry, like the workflow in the ThreeWayMerge

After merging here, the ISSN field gets updated.

[surajgojanur]

Hi, I would like to work on this issue.

I understand that the selected field value is not being applied correctly during the merge process. I will first reproduce the issue locally and then trace the merge logic to identify where the selected value is being ignored.

Please let me know if I can proceed or if there are any specific considerations I should keep in mind

[jabref-machine]

👋 Hey @surajgojanur, looks like you’re eager to work on this issue — great! 🎉 It also looks like you don't know how to assign issues to yourself. Please read our CONTRIBUTING.md to find out how. It will also guide you in other aspects of contributing to JabRef.

[surajgojanur]

/assign-me

[jabref-machine]

👋 Hey @surajgojanur, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and set up your local development workspace by following the steps in our workspace setup guidelines to get started smoothly.

For questions on JabRef functionality, you can consult the JabRef Guru. For questions related to the codebase, please start using DeepWiki.

In case you encounter failing tests during development, please check our developer FAQs!

Still facing issues or having more questions? Feel free to ask here on GitHub or on JabRef's Gitter chat. Please don't hesitate to open a (draft) pull request early on to show the direction you are heading towards if unsure.

Happy coding! 🚀

[ZiadAbdElFatah]

Hope you can close this issue will help a lot @surajgojanur.
Take a look on this PR #15267 you can continue working on it.
For the logic check this comment #15014 (comment).

[github-actions]

⏰ Assignment Reminder

Hi @surajgojanur, this is a friendly reminder about your assignment to this issue.

Warning

This issue will be automatically unassigned in 7 days if there's no activity.

Remember that you can ask the JabRef Guru or DeepWiki about anything regarding JabRef.
Additionally, our contributing guide has hints on creating a pull request and a link to our Gitter chat.

How to keep your assignment

If you are working on it, you can prevent automatic unassignment by:

• Submitting a draft pull request with your progress within 7 days
• Asking for the 📌 Pinned label if you need more time

We appreciate your contribution and are here to help if needed!