{"id":50747,"date":"2019-10-29T10:00:04","date_gmt":"2019-10-29T17:00:04","guid":{"rendered":"https:\/\/github.blog\/?p=50747"},"modified":"2024-08-01T07:46:21","modified_gmt":"2024-08-01T14:46:21","slug":"easier-bug-reporting-using-marker-io-for-github","status":"publish","type":"post","link":"https:\/\/github.blog\/enterprise-software\/easier-bug-reporting-using-marker-io-for-github\/","title":{"rendered":"Easier bug reporting using Marker.io for GitHub"},"content":{"rendered":"

Marker.io built an integration that adds additional bug reporting functionality to GitHub. Gary Gaspar, CEO and Co-founder at Marker.io, shares how you can streamline your bug reporting and issue reviewing workflows in this post.\u00a0<\/span><\/p>\n

\n

When your entire organization runs on GitHub, getting less technical teams like marketing, sales, and customer support to report sufficient details about bugs in issue trackers can be a real challenge. This leads to two problems.\u00a0<\/span><\/p>\n

First, bug reports are often unclear and incomplete, making it impossible for developers to understand the problem. Second, bug reports are often logged into \u201cwork-in-progress\u201d style repositories without ever being reviewed, reproduced, or prioritized. <\/span>Marker.io for GitHub<\/span><\/a> paired with GitHub\u2019s new transfer issue feature can help streamline your workflow with improved issue reporting and code reviewing.<\/span><\/p>\n

Step 1: Collect better bug reports in GitHub<\/span><\/a><\/h2>\n

Reporting bugs requires a number of steps and can be a time-consuming process. By using Marker.io for GitHub, you can help your development teams log actionable issues into GitHub in only three steps, without leaving your website:<\/span><\/p>\n

    \n
  1. Capture and annotate screenshots of the bug<\/span><\/li>\n
  2. Send bug reports straight to your GitHub repository<\/span><\/li>\n
  3. Hunt for more bugs<\/span><\/li>\n<\/ol>\n

    During the quality assurance process for our new pricing page, imagine that you run into a problem where the dollar amount on your pricing plan is mysteriously missing. Using the <\/span>Marker.io browser extension<\/span><\/a>, you can take a screenshot to highlight the issue, add visual annotations, and log it in just a few clicks\u2014without leaving the pricing page.<\/span>
    \n<\/span><\/p>\n

    <\/p>\n

    When a developer opens the GitHub issue tracker, any bugs reported through Marker.io are logged as new GitHub issues and always include actionable information.<\/span><\/p>\n

    <\/p>\n

    As you can see, all bug reports logged via Marker.io into GitHub include the following information:<\/span><\/p>\n