Hi everyone!
What was your previous process for reporting a bug compared to how Loom AI simplifies that experience? Give us examples of how Loom AI improved your workflow below and earn a new Kudos badge, “Workflow Champion”!
Learn how to use Loom AI workflows here!
My previous experience for reporting bugs was to take and edit screen shots and paste them into a bug ticket. Many orgs limit screen recording/capturing software, making a QA/Bug reporting job harder.
When we would have a QA Test Plan in Confluence we would tag it to the Jira Story we were testing and tag the bug to the story. Again, more screen shots. When allowed to use screen capturing software like Loom we can share in real time what the issue is and not have to do countless screenshots and editing of the images with arrows or notes. A massive time saver!
I feel like I should create a loom to show how I did it before and after with loom.
This is absolute 🔥🔥🔥!
I had a decent workflow lately with recording the replication of the bug with DashCam to give my developers access to the console logs. Then, I'd go back and recreate it again (or watch the DashCam video) and write up my bug report. Prior to using DashCam, I was taking numerous screenshots to visually explain each step.
Can't wait to log my next bug (err...wait...I don't want bugs...) with Loom!
@Kristie Riojas - do you know when/if Loom will get its own space in the online community?
@Amanda Barber
Loom WILL have its own spot in the Atlassian Community!The exact timeline is a tad up in the air right now while we tie up some loose ends on the backend. But rest assured, putting Loom in the spotlight within the Atlassian Community is a top focus and we'll make it happen as soon as we can!
It looks like you're new here. Sign in or register to get started.
