[MIG][18.0] Migration of mail_message_destiny_link_template (from 16.0)

[acsonefho]

Classic migration without any changes from 16.0 to 18.0 of mail_message_destiny_link_template.

[acsonefho]

Hello @rafaelbn @Shide Can you review this please 🙏

[rafaelbn]

/ocabot migration mail_message_destiny_link_template

[OCA-git-bot]

Sorry @rafaelbn you are not allowed to mark the addon tobe migrated.

To do so you must either have push permissions on the repository, or be a declared maintainer of all modified addons.

If you wish to adopt an addon and become it's maintainer, open a pull request to add your GitHub login to the maintainers key of its manifest.

[rafaelbn]

Thannk you @acsonefho !

@Shide I would recommend improve readme like this:

• Actual:

This module provides an email template to show which target records have been modified by a source record.

An email template already exists to show which source record a target record has been created or modified from.

Table of contents

[Use Cases / Context](https://gestion.ulzama.es/web#use-cases-context)
[Usage](https://gestion.ulzama.es/web#usage)
[Bug Tracker](https://gestion.ulzama.es/web#bug-tracker)
[Credits](https://gestion.ulzama.es/web#credits)
    [Authors](https://gestion.ulzama.es/web#authors)
    [Contributors](https://gestion.ulzama.es/web#contributors)
    [Maintainers](https://gestion.ulzama.es/web#maintainers)

Use Cases / Context

This module has been created to obtain a reverse template of message_origin_link (which allows you to link the origin record in the chatter).

• My proposal is ADD this example to be explicit for a funcional consultant with 0-tech knowledge.

"Example: When a purchase order generates an invoice, the invoice contains a message indicating its origin with a link to the purchase order. However, the purchase order does not record any message stating that it has generated an invoice. This module enables the purchase order to log a message indicating which invoice has been created from it, improving traceability."

[pedrobaeza]

Isn't OCA/mail a better host for this module?

[Shide]

@pedrobaeza It's only a template, but yes, could be a better repo to handle this module.

@acsonefho Maybe if you update README, you can also add this image #904 (comment)

[rafaelbn]

Please could you improve README with:

"This module provides an email template to show which target records have been modified by a source record.

Example: When a purchase order generates an invoice, the invoice contains a message indicating its origin with a link to the purchase order. However, the purchase order does not log any message stating that it has generated an invoice. This module allows developers to implement that functionality by providing a ready-to-use template.

⚠️ This module does not add functionality by itself. It is part of the server-ux repository and is intended for developers, who can implement the provided template as needed. The module includes an example code snippet to illustrate how to use it."

[acsonefho]

Hi @pedrobaeza is it possible to merge this one please?

[pedrobaeza]

/ocabot migration mail_message_destiny_link_template

Merging due to the reviews having issues that are not critical: the version bumping shouln't be done in the pre-commit commit, but on the migration one.

/ocabot merge nobump

[OCA-git-bot]

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 18.0-ocabot-merge-pr-1000-by-pedrobaeza-bump-nobump, awaiting test results.

[OCA-git-bot]

Congratulations, your PR was merged at c76d9a6. Thanks a lot for contributing to OCA. ❤️