Dev
Issue Title Generator
An issue title like "it's broken" is impossible to triage without reading the body. On a busy backlog that means it gets ignored. A clear title that states the what and where lets the team scan and prioritise without opening every ticket. Two inputs control the output: the Type dropdown (Bug, Feature, Task, or Improvement) and the Area or component field. The generator returns all templates for the chosen type shuffled: Bug titles follow [Bug] area + symptom; Feature titles follow [Feature] Add/Allow/Support; Task covers refactoring, testing, and updating; Improvement covers performance, error messages, and simplification. Choose the closest title and replace each bracketed placeholder with the specific detail. A filled-in title like "[Bug] login form fails when the email contains a plus sign" is immediately actionable; a bracket left in is an unfinished issue.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Choose the issue type.
- Name the affected area or component.
- Click Generate to see title options.
- Fill the brackets with the specific detail.
Use Cases
- •Writing scannable bug and feature titles
- •Keeping a backlog consistent and searchable
- •Avoiding vague, unactionable issue titles
- •Triaging faster with clear titles
- •Standardising issue format across a team
Tips
- →State the what and where so the title is scannable.
- →Keep a consistent type-tag convention across the tracker.
- →Be specific — "fails when X" beats "is broken".
- →Pair with the PR description generator when you fix it.
FAQ
what title templates are available for each type
Bug produces four templates covering failure conditions, wrong values, crashes, and edge cases. Feature produces three covering Add, Allow, and Support patterns. Task produces three covering refactoring, testing, and updating. Improvement produces three covering performance, error messages, and simplification.
why prefix the title with a type tag like [Bug]
A leading tag lets teammates scan the tracker and know the kind of work at a glance, and tools can filter or auto-label issues by matching it. It also prevents the vague one-word titles that are useless in a growing backlog.
should I keep the bracketed placeholders in the title
No — placeholders like [condition] or [capability] are prompts to fill in. Replace each one with the specific detail before filing. A title with brackets still in it is unfinished.
can I use these titles outside GitHub
Yes. The titles are plain text with no platform-specific syntax, so they work in Jira, Linear, GitLab, Azure DevOps, or any other tracker.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.