JotGo is a bug reporting and product feedback platform that lets users capture issues directly from a website or web application.
With just a few clicks, users can:
Instead of spending time asking follow-up questions, your team receives complete reports that are ready to investigate.
Most bug reports are incomplete.
A message like "The page is broken" doesn't tell developers enough to reproduce the issue.
JotGo automatically includes the important details that are usually missing, such as:
This saves time for both the person reporting the issue and the team fixing it.
Using JotGo is simple.
JotGo automatically attaches technical information in the background and sends everything to your workspace, where your team can review, assign and track the issue.
JotGo is designed for every team involved in building digital products.
Collect clear customer feedback without long email threads.
Create detailed bug reports in seconds with all the technical context included.
Receive reproducible issues instead of incomplete bug descriptions.
Report customer issues directly without requesting additional screenshots or technical information.
Understand UI problems with visual annotations and real user context.
Use a screenshot when you want to report:
If the issue requires multiple steps to reproduce, consider using a screen recording instead.
Your screenshot will open in the JotGo editor.
Before submitting your report, you can highlight exactly where the issue is.
Use the annotation tools to:
Annotations help developers understand the issue at a glance.
After capturing your screenshot, provide a few details about the problem.
Write a short, descriptive title.
Explain the issue in simple language.
Try to include:
When you submit a screenshot, JotGo automatically attaches useful technical details, such as:
This information helps developers reproduce and resolve issues more quickly.
Before submitting, take a moment to review your report.
Make sure:
A quick review can prevent follow-up questions later.
Click Create to send your report.
Your screenshot, comments, annotations and technical details are automatically added to your JotGo workspace, where your team can review, assign and track the issue.
Follow these tips to create more effective bug reports:
These small details can significantly reduce the time needed to understand and fix the problem.
Whether your team prefers a structured list or a visual workflow, JotGo provides two flexible views to help you manage work efficiently:
Switch between views at any time without losing information.
Managing bugs across emails, chat messages, spreadsheets and multiple tools can quickly become overwhelming.
A centralized repository helps your team:
Everything related to an issue stays together, making it easier to manage from report to resolution.
List View displays all your bug reports and feedback in a structured table, making it easy to review large numbers of issues.
This view is ideal for teams that need to search, sort and manage reports efficiently.
Each issue includes important information such as:
At a glance, you can understand the current state of every issue.
Quickly find the information you need using built-in search and filters.
You can filter by:
Filtering helps teams focus on the most relevant work without scrolling through long lists.
Organize issues based on what matters most.
For example, you can sort by:
Sorting helps you review reports in the order that best fits your workflow.
Canvas View provides a visual workspace where issues can be organized into groups based on your team's workflow.
Instead of reading through a list, you can move issues between different stages as work progresses.
This view is perfect for planning, sprint management and team collaboration.
Arrange issues into columns that match your development process.
For example:
Simply drag and drop issues between stages as their status changes.
Canvas View helps your team quickly understand:
This makes project progress easier to monitor during daily stand-ups and sprint reviews.
You don't have to choose one view permanently.
At any time, you can switch between:
Both views display the same issues, ensuring your team always works with the latest information.
Every report includes all relevant information in one place.
Depending on your workspace, an issue may include:
This eliminates the need to search through emails or chat conversations for additional context.
The centralized repository makes teamwork simple.
Your team can:
Everyone stays informed using a single source of truth.
To keep your repository organized:
A well-organized repository helps teams stay productive and reduces time spent managing issues.
A centralized repository ensures that every bug report and piece of feedback is easy to find, manage and track. Whether you're reviewing hundreds of reports in List View or planning work visually in Canvas View, JotGo keeps your entire team aligned and focused on delivering a better product.
Instead of switching between emails, chat apps or meetings, every conversation stays connected to the issue, making it easy for everyone to stay informed.
Comments help your team collaborate throughout the entire issue lifecycle.
With team comments, you can:
Having all discussions in one place makes collaboration more efficient and transparent.
Adding a comment is quick and simple.
Your comment is instantly visible to everyone with access to the issue.
Comments are a great way to keep your team informed as work progresses.
Examples of useful updates include:
Regular updates help everyone understand the current status of the issue.
If you need more information before resolving an issue, use comments to ask the reporter or your teammates.
Keeping questions within the issue ensures that all responses remain part of the issue history.
Need input from a specific team member?
Use @mentions to notify them directly in a comment.
Mentions help bring the right people into the conversation without creating separate discussions.
Every comment is linked to the issue, creating a complete conversation history.
This allows your team to:
Anyone joining the project later can quickly catch up by reading the conversation.
Comments can include supporting files to provide additional context.
Depending on your workspace settings, you can attach:
Attachments help teammates better understand the issue without leaving the conversation.
To keep discussions clear and productive:
Following these practices helps everyone stay aligned and reduces unnecessary back-and-forth.
Every bug report tells part of the story, but comments capture the collaboration behind the solution. By keeping discussions, updates and decisions together, JotGo helps teams communicate more effectively and resolve issues faster.
With a single link, you can provide secure access to specific bug reports or feedback, making collaboration faster and more convenient.
Sometimes you need feedback from people outside your team.
Public Shareable Links help you:
Instead of sending screenshots, videos and explanations separately, you can simply share one link.
Creating a public link is quick and easy.
Anyone with access to the link can view the shared issue based on your workspace permissions.
Depending on your workspace configuration, a shared link may include:
This provides stakeholders with all the context they need to understand the issue.
Public links are useful for sharing issues with:
Recipients can review the issue without needing full access to your JotGo workspace.
Instead of sending multiple emails or chat messages, share a single link that always reflects the latest information.
As the issue is updated, stakeholders can see:
This keeps everyone informed throughout the issue lifecycle.
To share issues securely:
Following these practices helps protect your project's information while making collaboration easier.
Collaboration doesn't stop at your internal team. Public Shareable Links make it easy to involve clients, partners and stakeholders in the development process without giving them full access to your workspace. Everyone stays informed using a single, always up-to-date source of information.
No. Anyone with the public shareable link can view the shared issue without signing in to JotGo.
No. Public Shareable Links provide view-only access. Recipients can review the issue, screenshots, recordings, comments and other shared details, but they cannot modify the issue or make changes to your workspace.
Yes. The public link always reflects the current state of the issue. Any updates made within JotGo-such as status changes, new comments or additional attachments-are automatically visible through the same shared link.
Whether you're a developer, project manager, QA engineer or team lead, the dashboard helps you make informed decisions using real-time data.
As your team handles more bugs and feedback, it's important to understand what's happening across your projects.
The Report Dashboard helps you:
With all your key metrics in one place, you can quickly understand where your team's attention is needed.
The dashboard provides a summary of your workspace and displays important metrics in an easy-to-read format.
Depending on your workspace configuration, you may see:
This gives you a clear snapshot of your current workload.
See how issues are distributed across different stages of your workflow.
For example:
This helps you understand how work is progressing and identify any stages where issues are getting delayed.
The dashboard helps you identify patterns in your reports.
You can track:
Understanding these trends helps your team focus on continuous improvement.
Quickly see how many issues belong to each severity level.
Examples include:
This allows your team to prioritize urgent work while keeping track of lower-priority tasks.
Managers can use the dashboard to understand how work is distributed across the team.
You may be able to view:
These insights help improve planning and balance responsibilities.
Use filters to focus on the information that's most relevant.
Depending on your workspace, you can filter by:
Filters make it easy to generate insights for a specific project, sprint or team.
The Report Dashboard isn't just for tracking issues-it's a tool for improving your workflow.
Use it to:
Regularly reviewing your dashboard helps your team make better decisions based on real data.
To get the most value from your dashboard:
A well-maintained dashboard provides more accurate and meaningful insights.
A Report Dashboard gives your team a clear view of what's happening across your projects. Instead of relying on individual updates, everyone can access the same real-time information to track progress, identify bottlenecks, and make informed decisions.
Access depends on your workspace role and permissions. Administrators, managers and other authorized users can view dashboard reports.
Yes. The dashboard reflects the latest issue activity as reports are created, updated or resolved.
Yes. You can apply filters such as project, date range, status, priority, assignee and more to view the information most relevant to your work.
This allows product, QA and engineering teams to work together using the tools they already use every day.
Managing bugs across multiple tools can lead to duplicated work and missed updates.
With the Jira integration, you can:
The integration ensures that bug reports move smoothly from discovery to development.
Before connecting Jira, make sure you have:
If you're unsure about your permissions, contact your Jira or workspace administrator.
Setting up the integration is quick and simple.
Once connected, your workspace is ready to sync issues with Jira.
You can create a Jira issue directly from any bug report.
The issue is created in Jira and linked to the original JotGo report.
When a Jira issue is created, JotGo can send important details such as:
This gives developers the context they need without manually collecting additional information.
Once linked, JotGo and Jira work together to keep your team informed.
Depending on your workspace configuration, you may be able to:
This keeps everyone working from the same information.
Integrating JotGo with Jira helps your team:
Your QA team can focus on reporting issues while developers continue working in Jira.
To get the most from the integration:
Following these practices helps maintain an organized and efficient workflow.
JotGo helps you capture complete bug reports, while Jira helps your development team plan and resolve them. By connecting the two, you create a seamless workflow where issues move from reporting to resolution without unnecessary manual work.
Yes. You need a Jira account with the appropriate permissions to create and manage issues.
Depending on your workspace configuration, you may be able to connect one or more Jira projects.
Synchronization depends on your organization's integration settings. Some workspaces support status updates or additional syncing between JotGo and Jira.
Whether you're working on a single application or managing several products, JotGo makes it easy to keep everything organized.
As your team grows, keeping issues organized becomes more important.
With Workspace & Project Management, you can:
A well-organized workspace helps your team find information faster and work more efficiently.
A workspace is the main area where your team collaborates in JotGo.
Your workspace contains:
Most organizations create one workspace for their company and manage multiple projects within it.
A project represents a specific application, website, product or service that your team is working on.
For example, you might create separate projects for:
Each project has its own issues, feedback and team members, making it easier to stay organized.
Adding a new project is simple.
Your project is now ready to receive bug reports and feedback.
If your organization works on several products, you can manage them all from a single workspace.
You can:
This helps teams stay focused while maintaining a central place for collaboration.
Assign the right people to the right projects.
Depending on their role, team members can:
This ensures everyone has access to the tools and information they need.
Each project can have its own configuration.
Depending on your workspace, you may be able to manage:
Keeping project settings up to date helps maintain consistency across your workspace.
To keep your workspace organized:
These practices make it easier to manage projects as your organization grows.
A structured workspace helps your team collaborate more effectively. By organizing work into dedicated projects, you can keep issues separated, improve visibility and ensure everyone is working on the right priorities.
Yes. You can create multiple projects within a workspace to organize different products, applications or teams.
Not necessarily. Access depends on the permissions assigned by your workspace administrator.
Yes. If a project is no longer active, you can archive it to preserve its history while keeping your workspace organized.
This helps developers understand complex workflows and reproduce issues more accurately.
Some issues cannot be fully explained with screenshots alone. Video recording captures every step performed before the issue occurs.
With Video Recording, you can:
This ensures your team has a complete picture of the reported issue.
Video Recording is useful whenever an issue involves multiple steps or navigation.
Common scenarios include:
Recording your workflow is simple.
The recording is automatically attached to your bug report.
During recording, JotGo captures everything happening within your browser session.
This may include:
This gives developers the full context needed to understand and reproduce the problem.
Once the recording is uploaded, your team can:
Everyone works from the same visual evidence, reducing misunderstandings.
Using Video Recording helps your team:
The more context you provide, the faster your team can identify the root cause.
For the best recording experience:
These practices help create clear and useful bug reports.
Some issues can't be fully explained with a single screenshot. Video Recording captures the complete workflow, including page navigation and browser tab switching, giving developers the context they need to investigate and resolve issues more efficiently.
Yes. You can freely switch between browser tabs within the same browser window during recording.
Yes. You can browse through your application normally while the recording is in progress.
Yes. Once you stop recording and submit your report, the video is automatically attached to the JotGo issue.
Before using JotGo, make sure:
If you're not sure which option your team uses, ask your workspace administrator.
Open the page where you found the issue.
Launch JotGo using one of the following:
The reporting panel will appear without interrupting your work.
Choose how you'd like to report the problem.
Capture a single image of the issue. This is best for visual bugs, layout issues or incorrect content.
Record your screen to show how the issue happens. This is useful for bugs that require multiple steps to reproduce.
Choose the option that best explains the problem.
Use JotGo's annotation tools to make your report easier to understand.
You can:
Clear visual feedback helps your team identify the issue faster.
Write a short description of the problem.
Include information like:
Simple, clear descriptions help developers reproduce the issue quickly.
When you're ready, click Submit.
JotGo automatically attaches helpful technical information, including:
This information helps developers investigate the issue without asking for additional details.
Once your report is submitted:
You don't need to send extra emails or screenshots - everything stays together in one report.
Use a video recording when reporting issues such as:
If a screenshot cannot fully explain the issue a screen recording is the best option.
JotGo will begin recording your actions while you reproduce the issue.
Perform the same steps that lead to the problem.
For example:
Try to move through each step naturally so your team can easily understand what happened.
Once you've captured the issue:
If the recording doesn't clearly show the issue, you can record it again.
Complete your report with a clear title and description.
Keep it short and specific.
Explain what happened and what you expected.
Include:
Example
Every video report automatically includes technical details to help your team investigate the issue.
Depending on your workspace settings, JotGo may collect:
This additional context helps developers reproduce the issue without asking for more information.
Take a moment to review your recording.
Check that:
A clear recording helps your team understand the issue much faster.
Click Create to send your report.
Your video recording, issue description and technical details are automatically added to your JotGo workspace, where your team can review, assign and track the issue.
Follow these tips to create more useful video reports:
These practices make it easier for developers to identify the root cause of the problem.
Screen recordings provide valuable context that screenshots alone cannot capture. They help developers see the exact sequence of actions, making it easier to reproduce and resolve complex issues.
Whether you're working with a small team or managing multiple projects, clear ownership keeps everyone accountable and work moving forward.
Without a clear owner, issues can remain unresolved or be worked on by multiple people at the same time.
Assigning an owner helps your team:
Every issue should have a single owner, even if multiple people collaborate on it.
Assigning an issue takes just a few clicks.
The selected user becomes the owner of the issue and is responsible for driving it toward resolution.
Sometimes priorities change or another team member is better suited to handle the issue.
You can easily reassign ownership at any time.
Common reasons to reassign an issue include:
The issue history keeps track of assignment changes, providing visibility into who handled the issue and when.
Team members can quickly see the issues assigned to them.
This helps them:
Managers can also review assignments across the team to ensure work is distributed evenly.
Ownership works together with issue status to keep everyone informed.
As work progresses, update the issue status to reflect its current stage.
Typical statuses include:
Keeping statuses up to date gives the entire team visibility into project progress.
Even though one person owns an issue, others can still contribute.
Team members can:
This keeps all discussions and decisions in one place.
Follow these recommendations to keep issue management efficient:
These habits help improve collaboration and prevent issues from being forgotten.
Clear ownership ensures that every issue has someone responsible for investigating, updating and resolving it. This improves accountability, reduces delays and helps teams collaborate more effectively from start to finish.
Whether you need a teammate's input or want to stay updated on an issue, notifications ensure you never miss important activity.
As projects grow, it's easy to lose track of conversations and updates.
Mentions and notifications help you:
Instead of manually informing teammates, JotGo automatically keeps everyone connected.
Need someone's attention? Simply mention them in a comment.
The mentioned user will receive a notification, making it easy for them to join the discussion.
Use mentions whenever you need input or action from a specific team member.
JotGo automatically notifies you when something important happens.
You may receive notifications when:
This helps you stay informed without having to monitor every issue manually.
Notifications help you keep track of the issues that matter most.
You can quickly see:
This allows you to respond faster and keep work moving.
To keep communication effective:
Thoughtful notifications help reduce unnecessary interruptions.
Every notification is linked to the related issue, allowing you to quickly open the report and review the latest activity.
This helps you:
To improve team communication:
Good communication leads to faster issue resolution and better collaboration.
Bug tracking is a team effort. Mentions and notifications ensure that the right people are informed at the right time, reducing delays and improving collaboration. Instead of chasing updates through emails or chat messages, your team can communicate directly within JotGo and keep every conversation connected to the issue.
You'll receive notifications for updates that are relevant to you, such as assignments, mentions, comments or status changes, depending on your workspace settings.
Yes. You can mention multiple team members in the same comment if their input is needed.
Yes. Your notification history allows you to review recent updates and quickly navigate to the related issue.
This makes it easy to collect feedback, answer questions and keep conversations in one place.
There are times when you need input from people outside your organization.
Guest access helps you:
Instead of asking guests to create an account, simply share the issue and invite them to comment.
If guest access is enabled for your workspace:
All comments are automatically added to the issue's conversation, making them visible to your team.
Depending on your workspace settings, guests may be able to:
This allows external reviewers to participate without needing full workspace access.
For security reasons, guests have limited permissions.
Depending on your workspace configuration, guests cannot:
This ensures that only authorized team members can make changes to your workspace.
Guests can provide feedback directly within the shared issue.
Every guest comment becomes part of the issue's conversation.
Your team can:
This creates a single source of truth for everyone involved.
To make guest collaboration effective:
Following these practices helps maintain an organized and secure collaboration process.
Great products are built through collaboration. Guest Access & Commenting allows clients, partners and stakeholders to participate in the feedback process without giving them full access to your workspace. This keeps communication simple, organized and connected to the issue from start to finish.
No. Guests can comment on a shared issue without signing in to JotGo.
The comment is added to the issue, making it immediately available for your team to review and respond to.
Guest Commenting makes it easy to collect feedback from clients, partners, testers and other stakeholders without requiring them to join your JotGo workspace.
These metrics provide valuable insights into how efficiently issues move from creation to resolution.
Tracking resolution metrics helps your team answer important questions such as:
By monitoring these metrics, you can make informed decisions and continuously improve your development process.
Average Resolution Time measures the average duration required to resolve issues across your workspace.
This helps you understand:
Regularly reviewing this metric helps identify long-term improvements in issue resolution.
Track the total number of issues your team has resolved within a selected time period.
This metric helps you:
Comparing resolved issues with newly reported issues provides a clear picture of overall project health.
Analyze resolution trends over time to understand how efficiently your team is resolving issues.
Trend analysis helps you:
Regularly reviewing resolution metrics helps your team:
Small improvements in resolution time can have a significant impact on customer satisfaction.
To make the most of your metrics:
Consistent monitoring helps your team maintain high service standards.
Resolution Metrics help your team understand how effectively issues are being managed. By tracking resolution performance, identifying delays and improving workflows, you can resolve issues more efficiently and deliver a better experience for your users.
Resolution Time is the total duration from when an issue is created until it is marked as Resolved or Closed.
Monitoring Resolution Time helps you evaluate team efficiency, identify workflow bottlenecks and measure the impact of process improvements over time.
By highlighting resolution trends and identifying delays, Resolution Metrics help teams optimize workflows, prioritize work effectively and improve overall productivity.
Instead of constantly checking your issue tracker, important updates are delivered directly to the Slack channels where your team already collaborates.
Keeping your team informed is essential for resolving issues quickly.
With the Slack integration, you can:
This helps your team respond to issues as soon as they happen.
Before connecting Slack, make sure you have:
If you're unsure about your permissions, contact your Slack workspace administrator.
Setting up the integration only takes a few steps.
Once connected, JotGo will begin sending notifications to your selected Slack channel.
JotGo can notify your team when important events occur.
Depending on your workspace settings, notifications may include:
This ensures your team is always aware of important updates.
You can create a Slack issue directly from any bug report.
The issue is created in Slack and linked to the original JotGo report.
Slack notifications can include useful information such as:
Team members can quickly open the issue from Slack to review the full details.
You can send different notifications to different Slack channels.
For example:
Organizing notifications by channel helps each team stay focused on the updates that matter to them.
When a notification appears in Slack, your team can immediately:
This reduces response time and keeps everyone aligned.
Connecting Slack with JotGo helps your team:
It brings issue tracking directly into your daily communication workflow.
To get the most value from the integration:
A well-configured notification system keeps your team informed without creating noise.
Fast communication leads to faster resolutions. By connecting JotGo with Slack, your team receives important updates where they already work every day. This reduces response times, improves collaboration and ensures that no critical issue goes unnoticed.
Yes. You'll need a Slack workspace and the necessary permissions to connect it with JotGo.
Yes. Depending on your workspace configuration, you can customize which events trigger Slack notifications.
Yes. If supported by your workspace settings, you can configure different channels for different projects or types of notifications.
By giving users the right level of access, you can protect sensitive information while enabling your team to work effectively.
As your team grows, not everyone needs the same level of access.
With User & Permission Management, you can:
This helps your organization stay secure while supporting smooth collaboration.
Adding new users to your workspace is quick and easy.
Once the invitation is accepted, the user can access the workspace based on the permissions you've assigned.
Roles define what users can do within JotGo.
Depending on your workspace configuration, common roles include:
Administrators have full access to the workspace.
They can:
Project Editors oversee project activities.
They can:
Guests have limited access.
Depending on your sharing settings, they can:
Guests cannot manage workspace settings or access private projects.
You can control which users have access to specific projects.
For each project, you can:
This ensures users only see projects relevant to their work.
As responsibilities change, you can update user permissions at any time.
You can:
Keeping permissions up to date helps maintain a secure workspace.
When someone leaves your team or no longer needs access, you can remove them from the workspace.
Removing a user:
This ensures your workspace remains secure without losing valuable project history.
To maintain a secure and organized workspace:
Following these practices helps protect your workspace while supporting efficient collaboration.
Every team member plays a different role in your development process. By assigning the right permissions, JotGo helps you maintain security, improve collaboration and ensure everyone has access to the tools and information they need - without exposing sensitive workspace data.
Yes. Workspace administrators can update user roles and permissions at any time.
No. Access depends on the projects and permissions assigned to each user.
The user immediately loses access to the workspace. Existing issues, comments and activity history remain available for your team.
This makes bug reports easier to understand and reduces back-and-forth communication between reporters and developers.
A screenshot is helpful, but adding annotations provides even more clarity.
With Integrated Annotation Tools, you can:
Visual annotations make bug reports more accurate and easier to review.
JotGo provides a variety of tools to help you explain issues clearly.
These tools help create professional and informative bug reports.
After capturing a screenshot:
Your edited image is included automatically when you submit the issue.
If your screenshot contains confidential data, use the Blur Tool before sharing it.
You can blur information such as:
This helps protect user privacy while still providing the context needed to investigate the issue.
Annotations help everyone understand the issue more quickly.
Developers can immediately see:
This reduces confusion and speeds up the investigation process.
Using annotation tools helps your team:
A well-annotated screenshot often provides more value than a long written explanation.
For the best results:
Simple and focused annotations are the most effective.
A picture is worth a thousand words-but an annotated picture is even better. By allowing you to highlight issues, add explanations and protect sensitive information, JotGo helps your team create clearer bug reports and resolve issues faster.
Yes. Before submitting your report, you can annotate the screenshot using the built-in editing tools.
Yes. You can edit, undo, or remove annotations before saving your screenshot.
Yes. The Blur Tool lets you hide confidential information before sharing your screenshot with your team.
Annotations remove guesswork by showing exactly where the problem is.
Instead of writing:
"The button on the page isn't working."
You can highlight the button, point to it with an arrow and add a comment explaining the issue.
This helps developers and designers identify the problem much faster.
JotGo provides a set of simple tools to clearly communicate visual feedback.
Point to a specific element or area on the screen.
Best for:
Draw a box around the affected area.
Best for:
Highlight smaller elements that need attention.
Best for:
Draw freely to emphasize important areas.
Best for:
Add notes directly to your screenshot.
Use comments to explain:
Hide sensitive or personal information before sharing.
You can blur:
This helps protect user privacy while sharing reports.
Your annotations become part of the bug report and are visible to everyone reviewing the issue.
Keep your annotations simple and focused.
✔ Highlight only the affected area.
✔ Add short, meaningful comments.
✔ Use arrows to indicate the exact location.
✔ Avoid covering important parts of the interface.
✔ Remove unnecessary drawings before submitting.
A clean and focused annotation makes reports easier to understand.
The issue is now immediately clear to anyone reviewing the report.
To create clear and helpful reports:
Well-annotated reports reduce misunderstandings and help teams resolve issues faster.
Visual feedback is often easier to understand than written descriptions alone. By combining screenshots with annotations, your team can quickly identify the issue, understand its impact and begin working on a solution without asking for additional clarification.
Using priorities and statuses together gives your team a clear understanding of what needs attention, what is being worked on and what has already been resolved.
As the number of reported issues grows, it becomes important to organize work effectively.
With priority and status management, your team can:
This creates a structured workflow that helps teams deliver fixes more efficiently.
Priority indicates how urgently an issue should be addressed.
When reviewing a new report, assign the appropriate priority based on its impact and urgency.
Common priority levels include:
Issues that prevent users from using the application or affect core functionality.
Examples:
These issues should be addressed immediately.
Important issues that significantly affect users but may have temporary workarounds.
Examples:
These issues should be prioritized for the next available fix.
Issues that affect usability but do not block core functionality.
Examples:
These can be scheduled alongside regular development work.
Minor issues with limited impact on the user experience.
Examples:
These can usually be resolved in future maintenance releases.
Status shows where an issue is in its lifecycle.
As work progresses, update the status to reflect the current stage.
A typical workflow includes:
The issue has been created and is waiting to be worked on.
Work on the issue is currently underway.
The issue is under Review / Testing.
The issue has been completed successfully.
The issue has been reviewed and approved.
Progress is temporarily prevented due to a dependency or obstacle.
The issue has been removed or is no longer being pursued.
The issue does not apply to the current project or scenario.
A previously closed issue has been reopened for further investigation or fixes.
As work moves forward, update both the priority and status when needed.
For example:
Keeping these fields up to date gives your team an accurate view of ongoing work.
JotGo makes it easy to find the issues that matter most.
You can filter reports by:
These filters help teams quickly identify urgent work and monitor overall progress.
To keep your issue tracker organized:
A consistent workflow improves visibility and keeps the team aligned.
Priority helps your team decide what to work on first, while status shows where each issue is in the workflow. Together, they provide a clear picture of your project's health and ensure that important issues receive the attention they deserve.
Yes. Priorities can be updated at any time if the impact or urgency of the issue changes.
Yes. For example, if QA finds that a fix doesn't resolve the problem, the issue can move from “In Review” back to In Progress or updated to Reopen. Also, if any user changes the status by mistake, it can be moved back to its previous status again.
Depending on your workspace configuration, your organization may customize priorities and workflow statuses to match its internal processes.
Role-Based Access Control is a permission system that grants users access based on their assigned role.
Instead of giving every team member the same level of access, you can define what each role is allowed to do.
This helps keep your workspace organized, secure and easy to manage.
Using roles and permissions helps your organization:
Whether you have five users or hundreds, role-based access keeps your workspace secure and well-organized.
Depending on your workspace configuration, you may have roles such as:
Administrators have full access to the workspace.
They can:
This role is typically assigned to team leads or workspace owners.
Managers oversee projects and team activities.
They can:
Managers help coordinate work across the team.
Members are responsible for reporting and resolving issues.
They can:
This role is suitable for developers, QA engineers, designers and product team members.
Workspace administrators can assign roles when inviting new users or update roles later if responsibilities change.
To assign a role:
The user's permissions are updated immediately.
Each role has a different set of permissions.
Depending on your role, you may be able to:
If you don't have permission to perform an action, you'll only see the features available for your role.
As your team evolves, responsibilities may change.
Administrators can update a user's role at any time to match their new responsibilities.
For example:
Keeping roles up to date ensures everyone has the right level of access.
To maintain a secure workspace:
These practices help protect your workspace and reduce the risk of accidental changes.
Not everyone needs the same level of access. By assigning roles and permissions, JotGo helps organizations protect sensitive information, reduce accidental changes and ensure every team member can focus on the tasks that matter most.
Yes. Workspace administrators can update user roles at any time.
Yes. If your organization requires it, multiple users can be assigned administrative permissions.
Features that require additional permissions may be hidden or unavailable. If you need access, contact your workspace administrator.
Whether you're reviewing a new feature, discussing a reported bug or validating a fix, everyone can stay aligned throughout the development process.
External stakeholders often provide valuable insights that help improve your product.
Collaborating directly in JotGo helps you:
Instead of managing feedback across emails, chat messages and meetings, everything stays connected to the relevant issue.
When you need feedback from someone outside your organization, simply share the issue using a secure shareable link.
Stakeholders can:
This gives everyone access to the same information without requiring full workspace access.
Stakeholders can provide feedback directly on the issue.
They can:
All feedback is automatically linked to the issue, making it easy for your team to review and act on.
As work progresses, stakeholders can stay updated on the latest developments.
They can see:
This reduces the need for manual status updates and follow-up emails.
External collaboration doesn't end after an issue is reported.
Stakeholders can participate at every stage, including:
Report bugs or share product feedback.
Answer questions from the development team and provide additional context.
Review proposed fixes and confirm whether the issue has been addressed.
Test the updated feature or bug fix and provide final confirmation.
This continuous collaboration helps ensure that issues are resolved correctly.
To make external collaboration more effective:
Following these practices helps build trust and improves communication.
Using JotGo for stakeholder collaboration helps your team:
Everyone works from the same information, making collaboration simpler and more effective.
No. External stakeholders can access shared issues and collaborate using a public shareable link without signing in to JotGo.
Stakeholders can review the shared issue and add comments directly on the issue page, making it easy to ask questions, share observations and validate fixes.
All stakeholder comments and discussions are attached to the issue, providing a complete history of feedback and collaboration in one place.
At the top of the dashboard, summary cards provide a quick overview of your project's current status:
Tracks the number of reported, resolved and cumulative open items over time. This chart helps you evaluate whether your team is resolving issues faster than new ones are being reported.
Displays the distribution of items across different workflow stages, such as:
This helps identify bottlenecks and monitor the progress of ongoing work.
Visualizes issues based on their severity levels, including:
Use this chart to quickly identify high-impact issues that require immediate attention.
Shows the number of bugs and feedback items assigned to each team member. This helps track workload distribution and identify ownership across the team.
Displays the average resolution time for each priority level, such as:
This report helps evaluate response efficiency and ensures high-priority issues are resolved within expected timelines.
Categorizes unresolved items based on how long they have remained open, for example:
Monitoring issue age helps teams identify stale items and prioritize long-pending work.
Use the filters in the top-right corner of the dashboard to customize the displayed data:
The Bug & Feedback Trends dashboard provides a visual overview of your project's bugs and feedback, helping you monitor issue trends, track project health and make informed decisions using real-time analytics.
The dashboard helps your team identify high-priority issues, monitor workload distribution, track resolution trends and uncover bottlenecks, enabling faster and more effective decision-making.
Yes. You can filter the dashboard by Date Range, Project and Issue Type to focus on the data most relevant to your analysis.
This integration helps product, QA and engineering teams collaborate efficiently while keeping the complete context of every reported issue.
Your development team shouldn't waste time copying bug details between tools.
With the Linear integration, you can:
By connecting JotGo with Linear, your team can focus on fixing issues instead of managing them.
Before connecting Linear, make sure you have:
Setting up the integration only takes a few minutes.
Once connected, your workspace is ready to sync issues with Linear.
You can create a Linear issue directly from any bug report or feedback item.
A new issue is created in Linear and linked to the original JotGo report.
When a Linear issue is created, JotGo can include:
This provides developers with all the context they need to investigate and resolve the issue.
Once the issue has been created in Linear, your team can continue working without losing visibility.
Depending on your workspace configuration, you can:
This keeps both teams aligned throughout the issue lifecycle.
Integrating JotGo with Linear helps your team:
Everyone works from the same information, reducing confusion and improving productivity.
To get the most from the integration:
Following these practices helps maintain an organized and efficient development workflow.
JotGo helps you capture detailed, high-quality bug reports, while Linear helps your engineering team plan and manage development work. By integrating the two, your team can move from bug discovery to resolution with less manual effort, better collaboration and complete visibility throughout the process.
Yes. You'll need a Linear account with permission to create issues in the selected workspace or team.
Yes. During setup, you can select the Linear team where JotGo will create new issues.
Yes. Each Linear issue includes a link back to the original JotGo report, making it easy to review screenshots, recordings, diagnostics and other supporting information.
Technical diagnostics are system details that help explain the environment in which the issue occurred.
Instead of asking questions like:
JotGo automatically includes this information with your report.
Depending on your workspace settings and permissions, JotGo may collect the following information automatically.
Identify the browser where the issue occurred.
Examples include:
This helps developers determine whether the issue is browser-specific.
JotGo records the operating system being used.
Examples:
This helps identify platform-specific issues.
Capture basic details about the device used to report the issue.
This may include:
These details are useful when troubleshooting responsive or display-related issues.
JotGo automatically records the page where the issue occurred.
This allows developers to open the exact page without asking you to copy and paste the URL.
Every report includes the date and time it was created.
This helps teams:
JotGo can attach browser console logs.
Console logs help developers identify:
These logs often provide valuable clues about the root cause of an issue.
JotGo can capture network activity while you reproduce the issue.
This helps identify:
Developers can use this information to understand whether the issue is related to the frontend, backend or network.
Without automatic diagnostics, developers often need to request additional information before they can begin troubleshooting.
With JotGo, everything is included in the initial report, helping teams:
The more context included in a report, the easier it is to investigate.
To create the most helpful reports:
Combining visual evidence with technical diagnostics creates a complete and actionable bug report.
By default, the diagnostic data is attached with the report without any human intervention. Some information may be hidden from the Guest user in the report.
No. JotGo automatically collects supported diagnostics in the background, allowing you to focus on describing the issue.
No. Technical information is captured automatically and attached to your report, so the reporting process remains quick and simple.
Instead of scrolling through hundreds of reports, you can narrow down your results using search, filters and sorting options.
Searching and filtering helps your team:
Whether you're a developer, QA engineer or project manager. advanced search makes issue management more efficient.
Use the search bar to quickly find issues using keywords.
You can search by:
The search results update instantly, helping you locate the information you need without browsing through the entire repository.
Filters help you display only the issues that match specific criteria.
Depending on your workspace configuration, you can filter by:
You can combine multiple filters to create more targeted results.
Using more than one filter helps you narrow down large lists of issues.
For example, you can view:
Combining filters allows you to focus on exactly what matters.
Once you've filtered your issues, you can sort them in the order that works best for you.
Common sorting options include:
Sorting helps you review issues in a logical and consistent way.
Frequently used filters can help you access important issues faster.
Examples include:
These shortcuts reduce the time spent searching for common views.
To get the most accurate search results:
A well-maintained repository makes searching faster and more effective.
As the number of reported issues grows, manually browsing through reports becomes inefficient. Advanced search and filtering help your team quickly find the right information, prioritize work and make informed decisions without wasting time.
Yes. You can combine multiple filters to narrow down your results and create highly specific searches.
Yes. Depending on your workspace configuration, search can include issue titles, descriptions, IDs, labels and other searchable fields.
No. Filters and search results only change your current view.
This helps your team resolve customer issues faster while providing better visibility across support and development.
Support teams are often the first to hear about product issues. The Zendesk integration makes it easy to share those issues with your engineering team.
With the Zendesk integration, you can:
By connecting Zendesk with JotGo, customer feedback becomes part of your development workflow.
Before connecting Zendesk, make sure you have:
Setting up the integration only takes a few steps.
Once connected, your support team can start linking Zendesk tickets with JotGo issues.
When a support ticket requires engineering attention, you can create a JotGo issue directly from Zendesk.
The issue is created in JotGo and linked to the original Zendesk ticket.
When an issue is created, JotGo can include:
This gives developers the complete context needed to investigate the issue.
Once the ticket and issue are linked, both teams can stay informed throughout the resolution process.
Depending on your workspace configuration, you may be able to:
This creates a smoother workflow between customer support and engineering.
Using JotGo with Zendesk helps your team:
Everyone works from the same information, improving efficiency and customer satisfaction.
To get the most from the integration:
These practices help ensure a smooth handoff between support and development.
Great customer support depends on fast communication between support and engineering teams. By integrating JotGo with Zendesk, you can ensure customer-reported issues are captured accurately, shared with developers quickly and resolved with full visibility throughout the process.
Yes. You'll need a Zendesk account with permission to access and manage support tickets.
Depending on your workspace configuration, multiple tickets related to the same bug can be associated with a single JotGo issue.
Yes. If synchronization is enabled, support agents can view the linked JotGo issue and follow its progress without leaving Zendesk.
Session Replay records how users interact with your application during a session. It captures user actions such as clicks, scrolling, navigation and form interactions, allowing your team to replay the session later.
This provides valuable context that helps developers understand what happened before, during and after an issue occurred.
Session Replay helps your team answer important questions like:
Having this context reduces guesswork and speeds up troubleshooting.
JotGo can capture:
This information creates a replay of the user's experience without requiring them to record their screen manually.
This makes it much easier to reproduce issues that are difficult to explain with text alone.
To review a recorded session:
This allows developers to investigate issues step by step.
Using Session Replay helps your team:
Instead of guessing what happened, your team can see it.
To get the most value from Session Replay:
Combining visual evidence, technical details, and session replay creates a complete picture of the issue.
No. Session Replay records interactions within the supported application or website, based on the user’s actions.
Yes, Session Replay is always enabled.
Any user other than a guest user, can view the Session Replay from the issue details.
This integration keeps product, QA and engineering teams connected while ensuring every issue includes the context developers need to resolve it quickly.
Managing bugs across different tools can slow down your development process.
With the Izio integration, you can:
By connecting both platforms, your team spends less time managing tasks and more time fixing issues.
Before connecting Izio , make sure you have:
Setting up the integration is quick and easy.
Once connected, your team can start creating Izio tasks directly from JotGo.
You can create an Izio task from any bug report or feedback item.
A new task is created in Izio and linked to the original JotGo issue.
When an Izio task is created, JotGo can include:
Developers receive all the information they need without requesting additional details.
After the task is created, your team can continue managing the work in Izio .
Depending on your workspace configuration, you may be able to:
This provides complete visibility from issue reporting to resolution.
Using JotGo with Izio helps your team:
Everyone stays aligned throughout the development process.
To get the most from the integration:
Following these practices helps your team work more efficiently.
JotGo captures complete and detailed bug reports, while Izio helps your team organize and manage development work. Together, they create a connected workflow that reduces manual effort, improves communication and helps your team deliver fixes faster.
Yes. You'll need an Izio account with permission to create and manage tasks in the selected project.
Yes. During setup, you can select the Izio project where JotGo will create new tasks.
Yes. Each Izio task includes a link back to the original JotGo issue, allowing developers to review screenshots, recordings, diagnostics and other supporting information whenever needed.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.
