161–170 of 240 posts
Earlier quoted context omitted.
[I work at Jam] We do have an internal build for Firefox.. it's coming :)
It would be great to have a FAQ page on your site mentioning this. I was on your docs page and did a search for "firefox" as well as "safari" in the search box and there were no hits at all. Seems like something that people would often be checking for.
Earlier quoted context omitted.
[I work at Jam] We do have an internal build for Firefox.. it's coming :)
Awesome, I will check back regularly. This looks like one of those tools that is genuinely really useful. I would love be able to tell my users to just fireup a browser extension and record a bug, rather than having to step them through how to capture all that data manually. Well Done! Bookmarking this page for the futuere: https://jam.dev/docs/downloads-and-browsers/browser-support
> but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took Ah ah. At one gig we had trained the users to always send a screenshot of the entire screen. People reviewing the tickets would dump them if the screenshot was cropped and the user warned: "No full screenshot, no ticket" . Why? The most important info was the time at which the error happened (…
Indeed, that's a great rule. Another one is "What URL was the browser on?" which is rarely ever in cropped screenshots but is visible in full screenshot
I built a similar tool in 2016 called Bugcam that does exactly this. It was also a chrome extension with the ability to tie console logs and network traffic to screenrecordings. Jam looks really polished and far more usable than the weekend hack I put together :) Well done! The explanation for why OP built Jam was precisely the motivation I had for building Bugcam. I had transitioned to a team in Europe as part of an…
I think this is really awesome. Our company has a monolithic giant that is full of tech debt and high support cost from our on premise web application. Half the battle is asking the clients to send screenshots or properly explain the issue. For us would be an easy sell if we could integrate natively with the apps front end tech stack.
This looks awesome. Any tips on getting my support people to actually use it?
Earlier quoted context omitted.
I see in the Security page [0] that you filter out headers that you think are PII or tokens. And I see that you're willing to receive feedback via email. I don't think this approach is scalable, for the main reason that sometimes we use custom headers to pass tokens. My suggestion is to have a setting that lists default headers you think should be obfuscated, and the user/team can remove and add to them as they like.…
[disclosure: I work at Jam] Yes! I think that's a great idea.
Kind of funny, I was just looking at adding similar functionality to an internal Chrome plugin I built because we struggle to get enough useful info in bug reports (being able to look at the HAR, in particular, is useful, but difficult to get users to do correctly). Two questions - 1) Any way to customize which headers/cookies get scrubbed? 2) Is there a way to get something like the lower-level export you can get by…
We don’t have a way to customize that yet but we absolutely need to build that
And yes! Network logs get captured and added to the bug report automatically and we have copy as curl too so you can retry the request locally
Knowing more up front about how the whole thing works would make me more inclined to try it, especially since I'm wary of tools that take liberties with what they capture and store.
Kind of funny, I was just looking at adding similar functionality to an internal Chrome plugin I built because we struggle to get enough useful info in bug reports (being able to look at the HAR, in particular, is useful, but difficult to get users to do correctly). Two questions - 1) Any way to customize which headers/cookies get scrubbed? 2) Is there a way to get something like the lower-level export you can get by…
Ha, that’s cool! We don’t have a way to customize that yet but we absolutely need to build that And yes! Network logs get captured and added to the bug report automatically and we have copy as curl too so you can retry the request locally
Being able to redact a few values would be really important for us (I just wrote Python scripts to clean the har files up), but I’m going to play around with it this weekend.