3 ms·
What if the element moves or is replaced in the next design iteration ? I’m not sure you want to be merging and splitting tickets on individual DOM elements to
by unilynx 4y ago
What if the element moves or is replaced in the next design iteration ? I’m not sure you want to be merging and splitting tickets on individual DOM elements to keep the comment history sane..
Though I would be interested in tooling that allows clients to simply create issues by clicking an element and then saving full context (dom, screenshot, url, form state, browser and session) with that issue. Something important is too often missing from a bug report.
But then the problem is getting the client to actually use that tool.
- Blahah 4y agoYes, you're describing some of the problems addressed by the open annotations standard and the tooling in that ecosystem.
- Ladyady 4y agoYbug.io is the best I've found for this purpose. The only thing it doesn't do is collect the DOM element information. The user can choose to send a report with a full-screen screenshot or annotate a part of it. It also sends console errors if you want it to.
- solardev 4y agoMost of the good tools like that do capture the context like that, while still making it easy for the end user. Even just a paragraph plus a screenshot plus the url plus the console is a great start, and that's all easy to capture automatically but hard to get from users manually. Then there is a pipeline from that into your issue manager. I've sent them into jira, Airtable, etc. for further refinement and work.