"New Feature" Github Issues Template

"New Feature" Github Issues Issue Template

Use our "New Feature" Github Issues issue template to help your teams build better, faster.

Magical.pm

Finding the Right Template For Your Team

Selecting the right Github Issues 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 Github Issues issue templates to help your team find what works. Our "New Feature" template, which you can find below, is a great starting point.

What Does "Right" Look Like?

The right Github Issues 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 Github Issues issue template can help you stay on the right track.

Stage-Appropriate

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

Flexible

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

Template

Our "New Feature" Template

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

Feature Overview

[Provide a detailed description of the new feature, including its purpose, functionality, and any relevant context.]

User Story

As a [specific role], I want [clearly define the goal or functionality], so that [explain the reason or benefit this feature provides].

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 "New Feature" issues with Magical.pm, the AI product management co-pilot.

Example

"New Feature" Template Example

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

Feature Overview

Implement the Hitchhiker’s Guide to the Galaxy Instant Information Retrieval System (HG2G-IIRS) to provide real-time, context-aware information on any topic. The system should be accessible across standard sub-ether networks and integrate with existing user interfaces.

User Story

As an intergalactic traveler, I want instant access to relevant survival information, so that I can navigate unfamiliar environments efficiently.

Acceptance Criteria:

• The system returns fast, contextually relevant responses.
• Entries dynamically update with the latest data.
• The interface is accessible via standard devices.
• If no relevant data exists, the system defaults to "Mostly Harmless."

Generating Github Issues Issues with Magical.pm

While you can use this template manually in Github Issues, 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 Github Issues issues. Magical.pm works hand-in-hand with Github Issues. When you generate a issue with Magical.pm, it is formatted in markdown, meaning it will perfectly copy into Github Issues, retaining everything from code blocks to headings. Internally, we copy issues from Magical.pm to Github Issues 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.

Skeptical? Try it now

Generate a issue with Magical.pm in seconds

Write lazy requirements"when the user types in the field, turn the button #5260FF"

Get perfectly formatted requirementsMagical.pm will return perfectly formatted requirements.

Copy and paste into your toolsBe it Linear, Jira, Confluence – or anything else. Magical.pm's requirements are in markdown format.

Go further with TemplatesSelect the perfect template for your use case.

Lazy RequirementsDescribe your product requirements in natural language.

Your CardReady for dev, in seconds.

A funny thing happens when writing a PRD takes seconds...You start shipping. A lot.

Try Magical.pm Free

Magical.pm

Use Magical.pm to Generate Perfect Github Issues Issues Every Time

Generate Github Issues Issues with Magical.pm