Tags
JiraSystemProject Management
Created
July 17, 2022
Although often desired not every bug or new functionality needs a fully filled out template. Some topics may not always apply or are too obvious to be filled in for that specific ticket. So, feel free to remove sections as needed or leave ‘N/A’ to indicate that it’s not applicable.
Also please note that the structure of given subjects are mere guidelines, if you feel a subject would be better explained in plain sentences, drawings or a whole different way then by all means feel free to remove the initial structure and implement it as you see fit.
⁉️ Questions
Questions and/or pressing matters in here need to be resolved as soon as possible, preferably before or shortly after starting the ticket.
- N/A
✍️ Description
What happens when the bug occurs? How many times has happened? Does the application crash? Does nothing happen at all? Is an error displayed? Please be as specific as possible.
- DescriptionHere
🦋 Expected Result
What should happen / what is expected in an ideal situation where the bug does not occur?
- ExpectedResultHere
🐛 Actual Result
What is actually happening in the current situation?
- ActualResultHere
🔎 Steps to Reproduce
Provide a step by step plan to mimic the bug. Attach any screenshots to the ticket if necessary.
- StepsToReproduceHere
📝 Suggested Approach
With knowledge of the current codebase, try to define a best suggested approach. Think of current components used, flow of data and UI elements.
TODO
👉 Final Remarks
Anything to take note off that is not properly defined yet. Think of out of scope notes, dependencies, anything to be extra cautious about and/or information about related issues.
- What to test and why?
- N/A
- Ideas for different scenarios?
- N/A
- Ideas for different examples?
- N/A
‣
‼️ Markdown version
💡 *Although often desired not every bug or new functionality needs a fully filled out template. Some topics may not always apply or are too obvious to be filled in for that specific ticket. So, feel free to remove sections as needed or leave ‘N/A’ to indicate that it’s not applicable.
Also please note that the structure of given subjects are mere guidelines, if you feel a subject would be better explained in plain sentences, drawings or a whole different way then by all means feel free to remove the initial structure and implement it as you see fit.*
# ⁉️ Questions
---
⛔ *Questions and/or pressing matters in here need to be resolved as soon as possible, preferably before or shortly after starting the ticket.*
- N/A
# ****✍️ Description****
---
💡 *What happens when the bug occurs? How many times has happened? Does the application crash? Does nothing happen at all? Is an error displayed? Please be as specific as possible.*
- DescriptionHere
# ****🦋 Expected Result****
---
💡 *What should happen / what is expected in an ideal situation where the bug does not occur?*
- ExpectedResultHere
# ****🐛 Actual Result****
---
💡 *What is actually happening in the current situation?*
- ActualResultHere
# ****🔎 Steps to Reproduce****
---
💡 *Provide a step by step plan to mimic the bug. Attach any screenshots to the ticket if necessary.*
- StepsToReproduceHere
# ****📝 Suggested Approach****
---
💡 *With knowledge of the current codebase, try to define a best suggested approach. Think of current components used, flow of data and UI elements.*
- [ ] TODO
# ****👉 Final Remarks****
---
⚠️ *Anything to take note off that is not properly defined yet. Think of out of scope notes, dependencies, anything to be extra cautious about and/or information about related issues.*
- **What to test and why?**
- N/A
- **Ideas for different scenarios?**
- N/A
- **Ideas for different examples?**
- N/A