DoerPath

How to Convert Feedback to GitHub Issues

When feedback represents actionable work, you can convert it directly to a GitHub issue. This guide shows you how to connect feedback to your development workflow.

Prerequisites

Before you begin:

  • You must be signed in as a team member
  • Your team must have a GitHub account connected
  • The project must have at least one linked GitHub repository
  • You need feedback to convert

Connecting GitHub

If you haven't connected GitHub yet:

Step 1: Go to Team Settings

Click your team name in the sidebar, then click Settings.

Step 2: Connect GitHub

Under Integrations or Connected Accounts, click Connect GitHub.

Step 3: Authorize Access

Follow the GitHub authorization flow. Grant access to repositories you want to use for issues.

Converting Feedback

Step 1: Navigate to Feedback

Go to your project's Feedback tab and find the feedback item you want to convert.

Step 2: Open the Feedback Detail

Click on the feedback item to open its detail view.

Step 3: Click Convert to Issue

Look for the Convert to Issue button (or Create GitHub Issue). Click it to open the conversion dialog.

Step 4: Select Repository

Choose which GitHub repository should receive the issue. Only repositories linked to this project appear in the list.

Step 5: Review Issue Content

The dialog pre-fills:

  • Title - From the feedback title
  • Body - From the feedback body, with metadata appended

You can edit both fields before creating the issue.

Step 6: Create the Issue

Click Create Issue to submit to GitHub.

Expected Result

After conversion:

  • A new issue is created in the selected GitHub repository
  • The feedback item shows a link to the created issue
  • The feedback status is automatically marked as Done
  • The submitter receives a notification (if they provided email)

Issue Format

The created issue includes:

[Original feedback body]

---
**Feedback Details**
- Type: Bug / Idea / Question
- Submitted: [date]
- Submitter: [name or "Anonymous"]
- Source: [link back to feedback]

This preserves context while keeping the issue focused on the actionable content.

When to Convert

Good candidates for conversion

  • Bugs with clear reproduction steps
  • Feature requests that align with your roadmap
  • Questions that reveal documentation gaps

Consider waiting

  • Vague feedback that needs clarification
  • Duplicate reports (link to existing issue instead)
  • Out-of-scope requests

Troubleshooting

"No repositories available"

Check that:

  • Your GitHub account is connected to the team
  • At least one repository is linked to this project
  • The GitHub connection has repository access

To link a repository:

  1. Go to project settings
  2. Find the Repositories or GitHub section
  3. Connect the desired repository

"GitHub connection required"

Your team hasn't connected a GitHub account. Go to team settings and connect GitHub.

"Permission denied"

Your GitHub token may need additional permissions. Reconnect GitHub with repository write access.

Issue created but feedback not updated

If the issue was created but the feedback status didn't change:

  • Refresh the page
  • Check if the link appears in the feedback detail
  • The status update may be slightly delayed

Alternative: Manual Linking

If you create an issue manually in GitHub, you can still link it:

  1. Open the feedback item
  2. Copy the feedback content to GitHub manually
  3. Add a comment or note with the GitHub issue URL
  4. Mark the feedback as Done

This approach works when automatic conversion isn't suitable.

Best Practices

  1. Review before converting - Edit the title and body for clarity
  2. Add context - Include relevant screenshots or logs from your investigation
  3. Use labels - Add appropriate labels in GitHub after creation
  4. Deduplicate first - Check for existing issues before creating new ones
  5. Batch similar feedback - Combine related items into a single comprehensive issue

Workflow Integration

With GitHub Projects

After conversion, drag issues to your GitHub Project board for sprint planning.

With PR References

Reference the issue number in PRs: Fixes #123 or Closes #123 to auto-link.

With Milestones

Assign converted issues to milestones for release tracking.

Next Steps

After converting feedback:

  • Review the created issue in GitHub
  • Add labels, assignees, or milestones
  • Track progress through your normal development workflow

Related

Was this page helpful?
How to Convert Feedback to GitHub Issues | Documentation | DoerPath