trabajo-afectivo/.gitlab/merge_request_templates/Default.md

## What does this MR do?

<!-- Is there a lot to say? Consider creating an issue. -->

## Screenshots  <!-- Optional -->

### Before

![alt text](https://example.com/before.png)

### After

![alt text](https://example.com/after.png)

## Notes

* This MR
  **does**  <!-- KEEP ONLY ONE -->
  does not  <!-- OF THESE LINES -->
  change more than 3 files / 100 lines of code.

  <!-- If so, what’s the connection? Or, could you split it into multiple MRs? -->

* This MR
  **does**  <!-- KEEP ONLY ONE -->
  does not  <!-- OF THESE LINES -->
  introduce new methods.

  <!-- If so, are they tested? -->

* This MR
  **does**  <!-- KEEP ONLY ONE -->
  does not  <!-- OF THESE LINES -->
  modify or remove existing methods.

  <!-- If so, did you modify/remove their tests, as well? -->

* This MR
  **does**  <!-- KEEP ONLY ONE -->
  does not  <!-- OF THESE LINES -->
  add to, modify, or remove existing test cases.

  <!-- If so, explain. -->

### Performance Impact  <!-- Optional -->

<!--
Does your MR optimize (or degrade) performance?
If so, apply the label and explain here.

Consider that some of OTRS’s customers had
HUNDREDS of agents, overviews, and groups,
over 2,000 tickets a day,
and over 20,000,000 (!) tickets in all.
How do your performance changes scale on a system of this size?

(Remember, these are not edge cases we can ignore;
they are really big customers, and we want to keep their business!)
-->

### Follow-up Required  <!-- Optional -->

<!--
Does your MR require coordination with the documentation/support teams?
If so, apply the label and explain here.
-->