Description
The boss stops moving after the arena changes. Damage still registers, but the encounter cannot finish.
Context attached to the ticket
Everything your team added before Trundle started the work.
Execution scopetrundleyou
codereviewqa
SEE WHAT HAPPENS AFTER THE PLAYTEST
Follow the issue from report to reviewed fix, with the original evidence still attached
Turn playtest findings into workable tickets
Capture the screenshot, reproduction steps and build details in one ticket, ready for the team to scope and act on.
Keep the fix tied to what the player found
Keep the player report, files and acceptance checks beside the code as the fix moves through development and review.
Check the result against the original report
Compare the completed change with the original report and return it to the build with review notes and QA evidence attached.
YOUR TEAM DECIDES WHAT MAKES THE BUILD
Trundle can carry the fix through development, review and QA. Your team keeps control of the build and what reaches players.
AUTOMATION SCOPE
DEVELOPMENTAUTOMATED
REVIEWAUTOMATED
QAAUTOMATED
MERGETEAM ONLY
Trundle handles
- Turns playtest reports into scoped tickets
- Keeps the original context attached
- Reviews the change against the ticket
- Runs QA before the work returns
Your team controls
- Which issues enter the sprint
- When a fix joins the build
- Which release branch it reaches
- What ships to players
MAIN BRANCHPROTECTED
FINAL DECISIONYOUR TEAM