diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 7da8e4fa8..05d65a579 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -9,15 +9,11 @@ n/a
 
 ## Checklist
 
-If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.
+<!-- If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that. -->
 
-* [ ] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix _(in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes)._
-* [ ] Does this PR require product documentation?
-  * [ ] If so, make sure the JIRA epic is labeled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
-* [ ] Does this PR require a product release notes entry?
-  * [ ] If so, fill in "Release Note Text" in the JIRA.
-* [ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
-  * [ ] If so, make sure it is described in the JIRA ticket.
+* [ ] Does the changes in PR need specific configuration or environment set up for testing?
+   * [ ]  if so please describe it in PR description.
+* [ ] I have added thorough unit tests for the change.
 * QE requirements (check 1 from the list):
   * [ ] Standard QE validation, with pre-merge tests unless stated otherwise.
   * [ ] Regression tests only (e.g. refactoring with no user-facing change).