Work as a QA engineer (SDET) includes bug detection and issue creation (or "defects" - a problem found during the product testing process, according to ISTQB).
Often IT engineers have KPI (Key Performance Indicator - indicator of achieving required performance by a person). And for QA engineers it's based on the number of created defects.
And here in the creation of a new issue is a lifehack, a simple way of process optimization and improving personal performance. As a bonus, it makes the process more transparent.
We will do this in Jira, one of the most popular bug tracking systems nowadays. But! This improvement could be applied to any in fact.
So, Jira provides the ability to configure templates for different task types and for different projects.
What we have to do - we need to configure the template for bug issue type in our project (below is the example, of how it must look at the end; detailed instruction of how it should be done by Jira admin could be found in official documentation).
The base of our template will be a Description block, where we need to create titles - problem, precondition, steps to reproduce (S2R), expected results, actual results, and definition of done (DoD, could be - automation is done, fixed on some exact environment, etc.).
Also, would be great to create a field Environment. It could be added as in the Description block with titles above and also it could be configured as a separate independent field.
Also, newly created ticked could be assigned to a team lead or to a product owner (depends on processes in a team).
What we gain - a more structured process of bugs creation, which helps to improve the time of ticker creation and time spent on reading it (then reading each time ticket with free form), as we are working with the framed structured template.
Profit👍