diff --git a/.gitlab/issue_templates/bug.md b/.gitlab/issue_templates/bug.md
index 3e9f22f83364fe8fac5d2c41e37b92c5453b06aa..9fe80fef4397f4fe7475699864388814f3b72d87 100644
--- a/.gitlab/issue_templates/bug.md
+++ b/.gitlab/issue_templates/bug.md
@@ -1,11 +1,9 @@
 # Reporters
-
 - name-of-proposer-1 (institution-of-proposer-1)
 - name-of-proposer-2 (institution-of-proposer-2)
 ...
 
 # Description
-
 Describe the bug.
 If needed, Attach logs and reports to your bug.
 If needed, feel free to point external content as references (journal paper, Youtube video, etc.).
@@ -15,7 +13,6 @@ If needed, feel free to point external content as references (journal paper, You
 - MicroK8s (include version and add-ons):
 - TeraFlowSDN (include release/branch-name/commit-id):
 
-
 ## TFS deployment settings
 - list of components deployed
 - particular configurations you applied
@@ -33,7 +30,9 @@ If needed, feel free to point external content as references (journal paper, You
 ## Expected behaviour
 - describe the expected behavior (if you know it)
 
-# References
+## Acknowledgements
+This work is funded by <FUNDING-ORGANISM> through the <CALL-NAME> <PROJECT-ACHRONYM> project with <PROJECT-ID/REFERENCE>.
 
+# References
 1. [Reference name](https://reference-url)
 2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.
diff --git a/.gitlab/issue_templates/enhancement.md b/.gitlab/issue_templates/enhancement.md
index 06ea401cf9bee0a1c46fa7fb3a4fa1ac4372f57c..f84f6056c83025e01610fa3768600443dc0f5530 100644
--- a/.gitlab/issue_templates/enhancement.md
+++ b/.gitlab/issue_templates/enhancement.md
@@ -1,20 +1,19 @@
 # Proposers
-
 - name-of-proposer-1 (institution-of-proposer-1)
 - name-of-proposer-2 (institution-of-proposer-2)
 ...
 
 # Description
-
 Describe your proposal in ~1000 characters.
 You can reference external content listed in section "References" as [Ref-1].
 
 # Demo or definition of done
-
 Describe which high level conditions needs to be fulfilled to demonstrate this feature implementation is completed.
 You can reference external content (example, demo paper) listed in section "References" as [Ref-2].
 
-# References
+## Acknowledgements
+This work is funded by <FUNDING-ORGANISM> through the <CALL-NAME> <PROJECT-ACHRONYM> project with <PROJECT-ID/REFERENCE>.
 
+# References
 1. [Reference name](https://reference-url)
 2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.
diff --git a/.gitlab/issue_templates/new-feature-with-design.md b/.gitlab/issue_templates/new-feature-with-design.md
index b6ae943b64ebed5c64509737975fc5f302181806..2af263c8d1e9eced5ffee43e8b64d01957cf0f4f 100644
--- a/.gitlab/issue_templates/new-feature-with-design.md
+++ b/.gitlab/issue_templates/new-feature-with-design.md
@@ -1,60 +1,52 @@
 # Proposers
-
 - name-of-proposer-1 (institution-of-proposer-1)
 - name-of-proposer-2 (institution-of-proposer-2)
 ...
 
 # Description
-
 Describe your proposal in ~1000 characters.
 You can reference external content listed in section "References" as [Ref-1].
 
 # Demo or definition of done
-
 Describe which high level conditions needs to be fulfilled to demonstrate this feature implementation is completed.
 You can reference external content (example, demo paper) listed in section "References" as [Ref-2].
 
-# References
+## Acknowledgements
+This work is funded by <FUNDING-ORGANISM> through the <CALL-NAME> <PROJECT-ACHRONYM> project with <PROJECT-ID/REFERENCE>.
 
+# References
 1. [Reference name](https://reference-url)
 2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.
 
 # Feature Design (for New-Features)
 
 ## Clarifications to Expected Behavior Changes
-
 Existing component logic and workflows between components that need to be altered to realize this feature.
 Remember to justify these changes.
 ...
 
 ## References
-
 List of relevant references for this feature.
 ...
 
 ## Assumptions
-
 Enumerate the assumptions for this feature, e.g., fix XXX is implemented and merged, specific configurations, specific
 components deployed.
 ...
 
 ## Impacted Components
-
 List of impacted components: Context, Device, Service, PathComp, Slice, Monitoring, ZTP, Policy, NBI, etc.
 Just an enumeration, elaboration of impacts is done below.
 
 ## Component1 Impact
-
 Describe impact (changes) on component1.
 ...
 
 ## Component2 Impact
-
 Describe impact (changes) on component2.
 ...
 
 ## Testing
-
 Describe test sets (unitary and integration) to be carried out.
 This section can include/reference external experiments, demo papers, etc.
 ...
diff --git a/.gitlab/issue_templates/new-feature.md b/.gitlab/issue_templates/new-feature.md
index 06ea401cf9bee0a1c46fa7fb3a4fa1ac4372f57c..f84f6056c83025e01610fa3768600443dc0f5530 100644
--- a/.gitlab/issue_templates/new-feature.md
+++ b/.gitlab/issue_templates/new-feature.md
@@ -1,20 +1,19 @@
 # Proposers
-
 - name-of-proposer-1 (institution-of-proposer-1)
 - name-of-proposer-2 (institution-of-proposer-2)
 ...
 
 # Description
-
 Describe your proposal in ~1000 characters.
 You can reference external content listed in section "References" as [Ref-1].
 
 # Demo or definition of done
-
 Describe which high level conditions needs to be fulfilled to demonstrate this feature implementation is completed.
 You can reference external content (example, demo paper) listed in section "References" as [Ref-2].
 
-# References
+## Acknowledgements
+This work is funded by <FUNDING-ORGANISM> through the <CALL-NAME> <PROJECT-ACHRONYM> project with <PROJECT-ID/REFERENCE>.
 
+# References
 1. [Reference name](https://reference-url)
 2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.