"Bug Report" Basecamp Template

"Bug Report" Basecamp Issue Template

Use our "Bug Report" Basecamp issue template to help your teams build better, faster.

Magical.pm

Finding the Right Template For Your Team

Selecting the right Basecamp issue template is important in building your product and project management workflow. Some teams prefer simple, sparse issues that get to the point, while others prefer complex, documentation-rich issues. Each team is different, and your template should evolve as your team's needs change. With that in mind, we've assembled a library of Basecamp issue templates to help your team find what works. Our "Bug Report" template, which you can find below, is a great starting point.

What Does "Right" Look Like?

The right Basecamp issue template will match your team's stage, maturity, and purpose. Early in the product development process, your team is likely small and working on proof of concepts, where flexibility and quick pivots are key to success. Your team will likely want the lightest-weight issue template possible at this stage, enabling quick iteration without the burden of unnecessary documentation. Your issue template will evolve with your team, and as your team grows, so will your processes. Even with team growth, it's important to document as little as possible to maintain agility. The phrase "as little as possible" is intentionally chosen. If you under-document, you will lack a history of your team's work, the decisions you made, and their "why." You don't want to over-document, either. A good barometer for this is to ask yourself, "Is someone going to read what I'm writing?" If the answer is "yes," you're probably on the right track. If the answer is "no" or "not really," you're probably over-documenting. Striking the right balance is key to maintaining your velocity, and selecting the right Basecamp issue template can help you stay on the right track.

1

Stage-Appropriate

Ensure your template strikes the right balance between over- and under-documenting.

2

Flexible

Maintain flexibility as your team grows by optimizing for the least documentation possible.

Template

Our "Bug Report" Template

You can copy and paste this Basecamp issue template into Basecamp to create your own, or use Magical.pm to generate it with AI.

Summary

[Provide a concise and clear summary of the issue here.]

Steps to Reproduce

[List the first step to reproduce the bug here.]
[List the second step to reproduce the bug here.]
[...continue listing all steps to reproduce...]

Expected Result

[Describe the expected result here (e.g., if the bug were not occurring, what should happen?)]

Actual Result

[Describe the actual result here (e.g., because the bug is occurring, what is happening?)]

To-Do:

• [Identify and list the first actionable task here.]
• [Specify the second actionable task here.]
• [...continue listing all relevant tasks...]

Acceptance Criteria:

• [Clearly define the first success condition or expected outcome here.]
• [Specify the second success condition or expected outcome here.]
• [...continue listing all acceptance criteria...]

Good PMs use templates. Great PMs use templates in Magical.pm.Generate "Bug Report" issues with Magical.pm, the AI product management co-pilot.

Example

"Bug Report" Template Example

Here's an example of our Basecamp issue template in action.

Summary

The Delorean Time Circuits are malfunctioning, preventing proper time travel execution. Users report that after setting a destination time and accelerating to 88 mph, the flux capacitor does not engage, leaving the vehicle stranded in the present.

Steps to Reproduce

Enter a valid destination time in the Time Circuits.
Accelerate the DeLorean to exactly 88 mph.
Observe that the flux capacitor does not activate, and time travel does not occur.

Expected Result

Upon reaching 88 mph, the flux capacitor should activate, generating 1.21 gigawatts of power and transporting the vehicle to the designated time.

Actual Result

The vehicle remains in the present, and the flux capacitor does not generate the required energy for time travel. A trail of fire is notably absent.

To-Do:

• Inspect and recalibrate the flux capacitor's power input.
• Verify plutonium or lightning strike energy source integrity.
• Debug the Time Circuits software for potential calculation errors.
• Ensure sufficient road space for acceleration (no mall parking lots).

Acceptance Criteria:

• Flux capacitor consistently activates at 88 mph.
• Time Circuits correctly set and maintain destination time.
• Vehicle successfully disappears and reappears in the target time period.
• No unexpected detours to alternate timelines.

Generating Basecamp Issues with Magical.pm

While you can use this template manually in Basecamp, it's also compatible with Magical.pm, our AI issue generator. Using Magical.pm, you can instantly turn natural language like "unsink the Titanic" (feeling brave?) into perfectly formatted Basecamp issues. Magical.pm works hand-in-hand with Basecamp. When you generate a issue with Magical.pm, it is formatted in markdown, meaning it will perfectly copy into Basecamp, retaining everything from code blocks to headings. Internally, we copy issues from Magical.pm to Basecamp daily, making our workflows significantly faster. This workflow strikes a healthy balance: everything we love about human-generated requirements – the details and context – without the cognitive load and time overhead of perfect formatting, grammar, and writing.

Magical.pm

Use Magical.pm to Generate Perfect Basecamp Issues Every Time

Generate Basecamp Issues with Magical.pm