69 lines
2.0 KiB
Markdown
69 lines
2.0 KiB
Markdown
### 🎟️ Evercatch Ticket
|
|
|
|
<!-- Required. Link to the Jira ticket. Use 'Resolves' to auto-close. -->
|
|
|
|
Resolves: [EC-XXX](<PROVIDE-LINK>)
|
|
|
|
### 🎯 Purpose & Impact
|
|
|
|
> Please provide a clear, high-level summary of the change and its intended impact. Why is this change valuable to the Evercatch platform?
|
|
|
|
### 🛠️ Key Changes
|
|
|
|
<!--
|
|
Please provide a bullet-point list of the technical changes you made.
|
|
This is the most important section for the reviewer.
|
|
-->
|
|
|
|
-
|
|
-
|
|
-
|
|
|
|
### 📸 Screenshots or Videos
|
|
|
|
<!-- If this PR includes UI changes, please provide a screenshot or a short video. This is the fastest way to get visual changes approved. -->
|
|
|
|
---
|
|
|
|
### ✅ Author's Definition of Done
|
|
|
|
<!-- Please check the boxes that apply. This is your declaration that the work is ready for review. -->
|
|
|
|
- [ ] I have performed a self-review of my own code.
|
|
- [ ] My code follows the style guidelines and architectural patterns of this project.
|
|
- [ ] I have added or updated tests that prove my feature works or my fix is effective.
|
|
- [ ] All new and existing tests pass locally with my changes.
|
|
- [ ] I have made corresponding changes to the documentation (if applicable).
|
|
|
|
<br>
|
|
|
|
<details>
|
|
<summary><strong>🔬 Reviewer's Guide & Additional Info (Click to Expand)</strong></summary>
|
|
|
|
---
|
|
|
|
#### Where should the reviewer start?
|
|
|
|
<!-- Optional: Give the reviewer a hint! e.g., "Start with `src/services/NewService.ts` as that contains the core logic." -->
|
|
|
|
#### 🏷️ Type of Change
|
|
|
|
<!-- This provides context for the change. Please check one. -->
|
|
|
|
- [ ] **FEAT**: A new feature
|
|
- [ ] **FIX**: A bug fix
|
|
- [ ] **DOCS**: Documentation only changes
|
|
- [ ] **STYLE**: Code style changes (formatting, etc.)
|
|
- [ ] **REFACTOR**: A code change that neither fixes a bug nor adds a feature
|
|
- [ ] **PERF**: A code change that improves performance
|
|
- [ ] **TEST**: Adding missing tests or correcting existing tests
|
|
- [ ] **CHORE**: Changes to the build process or auxiliary tools
|
|
|
|
---
|
|
|
|
</details>
|
|
|
|
---
|
|
|
|
|