BrowserStack

Product Management Assignment

Improving Adoption of JIRA Integration in Live

Submitted by,
Anup Kulkarni
Roll Number: 2311117
IIM Bangalore

NEXT
Problem Statement

2
 QA & Developers Face Different Efficiency Issues

QA Engineer Developer

Detail-oriented, values efficiency. Often under time- Analytical and logical, appreciate precision & clarity.
crunch. Thrives with freedom to experiment. Thrives when given actionable insights, remedies.

Goals: Efficiently identify & report bugs with minimal manual effort Goals: Quickly understand & replicate issues for timely resolution

Says Thinks Says Thinks

"I need a faster way to log "I hope I’m not missing any key "Why isn’t this report detailed "I need accurate data to
issues!" details in this report." enough? Which data is actually resolve this quickly."
useful?"

Does Feels Does Feels

Uses manual methods to log Frustrated by inefficiencies & Requests additional details Frustrated by delays and
bugs, sometimes skips less anxious about incomplete bug from QA engineers or values clear, actionable
critical details due to time reports. reproduces bugs manually. reports.
constraints.

3
 Pain-points Exist Across the User-flow

QA Engineer Developer

Choose the distro & browser Check assigned bug on Jira

Launch the webpage Launch BrowserStack Live

No simple way to identify obvious defects at

Conduct Manual Testing Choose distro & browser Extra steps required
each step

If bug/issue is found use the No record of steps taken to create the bug, Launch webpage
Report a bug feature requiring manual entry in description
Has to rely on description to
Recreate the scenario
recreate bug
Automatic Screenshot is
Need to manually highlight elements
taken, which can be edited
Use debugging tools like Limited debugging tools, no
inspect to find probable dedicated UI panel to ease
Add project, description, cause debugging
Manually enter details repeatedly
assignee, issue type

Experiment with other No suggestions about

Pop-up can be clicked to Other details required by org need to filled variables to find probable probable cause of failure in
track/edit bug on Jira separately on Jira website cause bug report

4
Assumption: The analysis covers only the post-Jira integration user flow, assuming successful integration for all users without drop-offs.
 Competitors Offer Interesting Solutions

Offers customizable bug templates with pre-filled session data.

Gallery to track past screenshots

Dedicated Dev Tools Tab

Real-time collaboration tools for discussing
bugs.

5
 Solutions Should Focus on Efficiency Gains
QA Engineer Focused Developer Focused

Enhanced Jira Window Live Test Steps Tracking Session Link Generation Debugging Console

Consistent Design Defect Highlighting Session Link Generation Dedicated Debugging Tab

Design the bug report window to mirror Monitor console errors and highlight Generate a link that directly launches Introduce debugging tab to reduce
the Jira website interface for a elements related to those errors for the session where the bug was clutter while debugging on various
seamless experience. easier identification. created. devices and resolutions.

Auto-Prefill Details Interaction Tracking Link in Bug Description GenAI-Driven Defect Analysis

Prefill details such as project name, Record mouse clicks, inputs, & other Include the session link in the Provide potential sources of defects &
assignee, and issue type based on interactions, which can be attached to description to provide developers with solutions derived from GenAI, based
previously submitted bugs. the bug report to help reproduce bug. easy access for debugging. on available debug information.

Error-Based Description

Automatically generate a possible

description from console errors (e.g.,
"UI element failed to render").

6
Assumption (Enhanced Jira Bug Filling Window): Jira has required public APIs.
Detailed Solution – Enhanced Jira Window

7
Feasibility

8
Measuring Success Requires Holistic Approach

QA Engineer Developer
Adoption

• % Users Enabling Jira Integration

• Jira Integration bugs per user per session
Effectiveness

• Time to file bug

• % automated fields in bug reports