Overview
Gitea’s issue tracking system provides a complete solution for managing bugs, feature requests, tasks, and discussions. With support for labels, milestones, assignments, and rich markdown content, teams can effectively organize and track their work.Creating Issues
Fill in Details
- Title: Concise description of the issue
- Description: Detailed information with markdown support
- Labels: Categorize the issue (bug, enhancement, etc.)
- Milestone: Associate with a project milestone
- Assignees: Assign team members
- Projects: Link to project boards
Issue Creation from Code
Issue Templates
Standardize issue creation with predefined templates:- Markdown Templates
- YAML Templates
Create issue templates in
.gitea/ISSUE_TEMPLATE/ or .github/ISSUE_TEMPLATE/:Labels
Categorize and filter issues with labels:Creating and Managing Labels
Label Properties
- Name: Label identifier
- Description: Purpose of the label
- Color: Visual identification (hex color)
- Exclusive: Only one label from group
Default Labels
bug: Something isn’t workingenhancement: New feature or requestdocumentation: Documentation improvementsduplicate: Duplicate issuewontfix: Will not be worked on
Scoped Labels
Create exclusive label groups using the formatscope/item:
Scoped Label Examples
Scoped Label Examples
Priority Labels (exclusive)
priority/lowpriority/mediumpriority/highpriority/critical
status/needs-triagestatus/in-progressstatus/blockedstatus/ready-for-review
component/apicomponent/uicomponent/databasecomponent/auth
When a scoped label is applied, any existing label with the same scope is automatically removed.
Milestones
Organize issues into release cycles or project phases:Creating Milestones
Create Milestone
Click New Milestone and provide:
- Title: Milestone name (e.g., “v1.0.0”, “Q4 2025”)
- Description: Goals and scope
- Due Date: Target completion date (optional)
Milestone Management
Milestone completion percentage is automatically calculated based on open vs. closed issues.
Assignments
Assign issues to team members for accountability:Assigning Issues
- Web Interface
- Via Comments
Single Assignment
- Open the issue
- Click Assignees in the sidebar
- Select one or more assignees
- Click outside to save
- Select multiple issues with checkboxes
- Click Actions dropdown
- Choose Assign to…
- Select assignee(s)
Issue Comments
Collaborate through threaded discussions:Comment Features
Rich Content
- Full markdown support
- Code blocks with syntax highlighting
- Image and file attachments
- Emoji reactions
- @mentions for notifications
Actions
- Edit comment history
- Delete comments
- Quote reply
- React with emoji
- Mark as resolved
Slash Commands
Perform actions directly from comments:Issue References
Link related issues and pull requests:Reference Syntax
- Same Repository
- Cross-Repository
- Commit References
Dependencies
Track issue dependencies to manage blockers:Time Tracking
Track time spent on issues:Estimate Time
Set time estimates for planning:
- Add estimated time in issue
- Use format:
2h,30m,1d 4h - Update estimates as needed
Track Time
Record actual time spent:
- Start/stop timer in issue
- Manually add time entries
- View total time spent
- Compare estimate vs. actual
Issue Filtering and Search
Filter Options
Available Filters
Available Filters
Status
- Open issues
- Closed issues
- All issues
- Created by specific user
- Created by you
- Assigned to user
- Assigned to you
- No assignee
- Has specific label(s)
- Has no labels
- Label combinations (AND/OR)
- In specific milestone
- No milestone
- Newest first
- Oldest first
- Most commented
- Recently updated
- Least recently updated
Search Syntax
Issue Notifications
Automatic Notifications
- Issue creation
- Assignment changes
- Mentions (@username)
- Comment replies
- Status changes
Subscription Management
- Watch repository (all issues)
- Subscribe to specific issues
- Unsubscribe from issues
- Configure notification preferences
Issue Locking
Lock conversations to prevent further comments:Locked issues can still be reopened, closed, or modified by users with write access. Only commenting is restricted.
Closing Issues
Manual Closure
- Click Close button in issue view
- Add closing comment explaining resolution
- Use
/closeslash command in comment
Automatic Closure
Issues are automatically closed when pull requests with closing keywords are merged:Best Practices
Issue Management Tips
Issue Management Tips
Writing Good Issues
- Use clear, descriptive titles
- Include reproduction steps for bugs
- Add relevant context and screenshots
- Use templates for consistency
- Apply labels immediately
- Set milestones for release planning
- Assign owners for accountability
- Use projects for kanban-style tracking
- Triage new issues regularly
- Keep issue count manageable
- Close duplicates and outdated issues
- Link related issues and PRs
- Be respectful and constructive
- Update progress in comments
- Use reactions instead of “+1” comments
- Reference commits and PRs
See Also
- Pull Requests - Code review workflow
- Projects - Kanban boards for issue tracking
- Repositories - Repository management