Amazing! And yes - we have integrations with several Project Management tools (and Slack!) to:

• Help you save time by not going back and forth between the site you're QA'ing and the PM tool you're logging bugs in.
• Make sure the engineers you're working with don't have to search in Slack, email, spreadsheets etc. for all the different bugs :)

An idea I'm also interested in is whether having an "official tool" (rather than a spreadsheet) for design QA will help give it the clout it deserves within the product development process. Let me know if you have any thoughts about that!

Lastly, if you get a chance to try it out - I'd really love to hear your feedback!

I used to use Airtable or Google sheets to record all of the issues. Within the sheet, I'd have multiple columns, which included:

• Priority (P1, P2, P3)
• Details (usually the CSS changes with some notes)
• The page URL
• Screenshot of the issue on the web page (would often annotate using Skitch or Annotate)
• Sometimes would take a screenshot of the Artboard or refer back to InVision.

After creating this, I'd either put this into Jira or work with the engineer from the spreadsheet directly. I've also done the whole "awkwardly sit over an engineer's shoulder for hours" and go pixel by pixel. I often find this to be nice and uncomfortable :)

The problem I usually faced was design QA was never "official" or viewed as important. Because of this (often times) all of the bugs I'd record would end up never getting fixed - womp :(

This frustrated me so much that I built a tool to help solve this problem for designers. You can check it out/try it for free here: www.toyboxsystems.com - would love to hear your thoughts!

Love this :)