From 5d99042d4c806d16236d41185366bef45c05c558 Mon Sep 17 00:00:00 2001
From: jf-cbd <jf-cbd@users.noreply.github.com>
Date: Fri, 4 Sep 2026 10:24:48 +0200
Subject: [PATCH] :memo: Update enhancement.yml and pull_request_template.md

---
 .github/ISSUE_TEMPLATE/enhancement.yml |  1 +
 .github/pull_request_template.md       | 10 ++++++----
 2 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/enhancement.yml b/.github/ISSUE_TEMPLATE/enhancement.yml
index e66458f087..1676cd1847 100644
--- a/.github/ISSUE_TEMPLATE/enhancement.yml
+++ b/.github/ISSUE_TEMPLATE/enhancement.yml
@@ -8,6 +8,7 @@ body:
         Please explain why you're creating this issue :
         - Please describe what's your improvement proposition.
         - Then tell us if you're willing to create a PR for this enhancement ? If so, we'll indicate in the issue if we're interested in it.
+        - The more users are affected and the greater is the impact, the more likely this improvement will be accepted. If you identified a bug and have an improvement proposition, please use the 'Bug report' template instead."
 
   - type: textarea
     id: enhancement_details
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index bd2971542f..6e77cfef18 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,6 +1,7 @@
 <!--
 IMPORTANT: Before creating your PR, please create an issue first to know if Combodo is interested in your contribution (not needed for translations PR).
 Since we may refuse a PR, it's preferable to create an issue first, to avoid spending time coding something that won't be accepted.
+PR that will benefit the most users and has a greater impact on the product are more likely to be accepted, so please explain your use case and why you think it would be useful for the community.
 
 Once you've done it, and we confirmed we're interested in it, please follow the guidelines within this PR template before submitting it, it will greatly help us process your PR. 🙏
 
@@ -9,10 +10,10 @@ Any PRs not following the guidelines or with missing information will not be con
 
 ## Base information
 
-| Question                                                                        | Answer                               |
-|---------------------------------------------------------------------------------|--------------------------------------|
-| Related to a SourceForge thread / Another PR / A GitHub Issue / Combodo ticket? | <!-- Put the URL -->                 |
-| Type of change?                                                                 | Bug fix / Enhancement / Translations |
+| Question                                                                        | Answer                                |
+|---------------------------------------------------------------------------------|---------------------------------------|
+| Related to a SourceForge thread / Another PR / A GitHub Issue / Combodo ticket? | <!-- Put the URL or ticket number --> |
+| Type of change?                                                                 | Bug fix / Enhancement / Translations  |
 
 ## Symptom (bug) / Objective (enhancement)
 
@@ -70,6 +71,7 @@ Explain in details how you are proposing to solve this:
 Don't remove these lines, check them once done.
 -->
 
+- [ ] If my PR is a bug fix or an enhancement, I opened an issue that got reviewed and approved by Combodo
 - [ ] I have performed a self-review of my code
 - [ ] I have tested all changes I made on an iTop instance
 - [ ] I have added a unit test, otherwise I have explained why I couldn't