← Back
Use Case

Cord for bug reporting

Nimrod PriellNimrod Priell
  • Product
Comparison between sending a mark up using cord, and sending a mark up without cord

QA doesn’t have to slow you down

Report bugs in 1 step

“It’s like having access to screenshots, Slack, Jira and our site without having to go to all 4.” Turn your comments on Cord into issues and alert your team via Slack.

Avoid unnecessary back and forths

Give your teammates everything they need: a screenshot of the issue, exactly where and when it appears plus a pin on the actual site or product.

Don’t lose track of what’s been done

Avoid the “What’s the status on __?” messages. Update the status and priority of any bugs you find in Cord or your task manager.

Key features for product teams

  • A bug tracking tool that doesn’t feel like a chore to install: Cord is completely self-serve – no snippets of code to add. Download the browser extension and you can start reporting bugs in seconds.
  • Never send a screenshot again with whiteboard-style annotations: Add Google Doc-style comments and drop pins on your website or product to show the team exactly where you’re talking about.
  • Take issue creation off your plate: Connect Jira, Asana, or whatever task manager you use to automatically create, assign, and update tasks without ever changing tabs.
  • Connected to Slack so you don’t miss a *ping: *Cord comments go straight to Slack, with links back to the tool with in-line annotation and comments, so you can chat about it in Slack or go right to the page the bug appears on.