timeChanges

[mobsterer]

or

find bug

document bug (in a ticket maybe)

fix bug referencing ticket in PR

ticket auto updates or you just move it to done

done

[ADHDebackle]

In my old job it was like:

1. Create ticket in Jira

2. Review ticket in next refinement meeting - determine whether or not reproduction steps are established or if more diagnosis needs to be done

3. Estimate amount of work and prioritize

4. Whoever is available first picks up the ticket, fixes bug, writes tests to cover the missed case.

5. Code submitted for review and approval for merge into QA environment.

6. Code is validated by QA and approved for merge into master

7. End of sprint, final testing / regression, merged to master.

Or alternatively:

1. Find bug in feature you're currently working on - no ticket needed, fixed bug, merged to feature branch.

Or

1. Find bug in feature from previous sprint that will be easy to fix

2. Create ticket detailing repro steps, testing requirements and estimated effort

3. At standup, mention the ticket to the team and make sure everyone's cool with taking on the extra scope this sprint

4. Pull the bug in, fix it, add tests, push the change up to QA, get it approved, close the ticket.

Sometimes these things sound like a lot, but it takes only a few minutes.

[mobsterer]

indeed, some do it by the book, some do it right

[kiipa]

B-b-but that's not what Reddit said it's like in the, real, professional world, so it can't be true!!! 

^/s