#137 - Update to spring 2025 standards

.github/ISSUE_TEMPLATE/bug_report.md

@@ -2,7 +2,7 @@
 name: Bug report
 about: Create a report to help us improve
 labels: 'bug'
-
+type: 'Bug'
 ---
 
 ## Describe the bug
@@ -21,5 +21,10 @@ A clear and concise description of what you expected to happen.
 ## Screenshots
 If applicable, add screenshots to help explain your problem.
 
+## Desktop (please complete the following information):
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
 ## Additional context
 Add any other context about the problem here.

.github/ISSUE_TEMPLATE/epic_task.md

@@ -0,0 +1,14 @@
+---
+name: Epic
+about: A larger task consisting of more deliverables
+labels: 'epic'
+type: 'Epic'
+---
+
+## Background
+A clear and concise intro into the situation.
+
+## Goal
+The goal that epic wants to achieve.
+
+[Add actionable subtasks or even epics]

.github/ISSUE_TEMPLATE/feature_request.md

@@ -2,7 +2,7 @@
 name: Feature request
 about: Suggest an idea for this project
 labels: 'enhancement'
-
+type: 'Feature'
 ---
 
 ## Background

.github/ISSUE_TEMPLATE/operative_task.md

@@ -0,0 +1,10 @@
+---
+name: Operative task
+about: Issue template for operational tasks.
+labels: 'infrastructure,no RN'
+type: 'Task'
+---
+
+## The task
+
+Short description of the task. 

.github/ISSUE_TEMPLATE/spike_task.md

@@ -2,7 +2,7 @@
 name: Spike
 about: Issue template for spikes, research and investigation tasks
 labels: 'spike'
-
+type: 'Task'
 ---
 
 ## Background
@@ -20,14 +20,12 @@ Feel free to add information about why it's needed and what assumptions you have
 
 The list of desired outcomes of this spike ticket.
 
-```[tasklist]
 ### Tasks
 - [ ] Questions have been answered or we have a clearer idea of how to get to our goal
 - [ ] Discussion with the team
 - [ ] Documentation
 - [ ] Create recommendations and new implementation tickets
 - [ ] item here..
-```
 
 ## Additional Info/Resources [Optional]
 

.github/workflows/check_pr_release_notes.yml

@@ -31,9 +31,10 @@ jobs:
           python-version: '3.11'
 
       - name: Check presence of release notes in PR description
-        uses: AbsaOSS/release-notes-presence-check@v0.2.0
+        uses: AbsaOSS/release-notes-presence-check@v0.3.0
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:
           github-repository: ${{ github.repository }}
           pr-number: ${{ github.event.number }}
+          skip-labels: 'no RN'