{"id":2627,"date":"2026-11-11T14:54:41","date_gmt":"2026-11-11T14:54:41","guid":{"rendered":"https:\/\/motoshare.in\/blog\/?p=2627"},"modified":"2026-11-11T14:54:43","modified_gmt":"2026-11-11T14:54:43","slug":"tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools","status":"publish","type":"post","link":"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/","title":{"rendered":"Tracking, Triage, and Technical Resolution: How to Evaluate Bug Tracking Tools"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A software defect discovered in production is more than an inconvenience; it represents operational downtime, customer churn, and developer distraction. When bugs are reported across fragmented Slack messages, customer support emails, and uncurated spreadsheets, critical issues get lost, engineers waste hours attempting to reproduce defects from vague descriptions, and regression cycles slip past release deadlines.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Bug tracking tools<\/strong> centralize the intake, prioritization, assignment, and resolution of software defects\u2014providing structured reproduction steps, stack-trace attachments, automated triage workflows, and tight integration with source code repositories. Evaluating bug tracking software requires distinguishing between <strong>enterprise agile issue-tracking platforms<\/strong>, <strong>high-velocity developer-first task suites<\/strong>, <strong>automated exception and crash reporting engines<\/strong>, and <strong>lightweight visual feedback capture tools<\/strong>.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_85 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/#Five_Core_Capabilities_of_Modern_Bug_Tracking_Systems\" >Five Core Capabilities of Modern Bug Tracking Systems<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/#Leading_Bug_Tracking_Tools\" >Leading Bug Tracking Tools<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/#Jira_Software_by_Atlassian\" >Jira Software (by Atlassian)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/#Linear\" >Linear<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/#GitHub_Issues_and_Projects\" >GitHub Issues and Projects<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/#GitLab_Issue_Tracking\" >GitLab Issue Tracking<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/#Sentry_Automated_Application_Performance_Error_Tracking\" >Sentry (Automated Application Performance &amp; Error Tracking)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/#Bugzilla_and_Redmine_Self-Hosted_Open-Source_Veterans\" >Bugzilla and Redmine (Self-Hosted Open-Source Veterans)<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/#Bug_Tracking_Tools_Comparison\" >Bug Tracking Tools Comparison<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/#Common_Bug_Tracking_Pitfalls_to_Avoid\" >Common Bug Tracking Pitfalls to Avoid<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/motoshare.in\/blog\/tracking-triage-and-technical-resolution-how-to-evaluate-bug-tracking-tools\/#Selecting_the_Right_Bug_Tracking_Tool\" >Selecting the Right Bug Tracking Tool<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Five_Core_Capabilities_of_Modern_Bug_Tracking_Systems\"><\/span>Five Core Capabilities of Modern Bug Tracking Systems<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A generic to-do list cannot manage software quality; production bug tracking platforms deliver five technical capabilities:<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li><strong>Structured Defect Intake and Reproduction Fields:<\/strong> Enforcing mandatory defect metadata\u2014including software version\/commit hash, environment (staging, production), device\/browser OS, severity vs. priority matrices, expected vs. actual behavior, and reproduction steps.<\/li>\n\n\n\n<li><strong>Crash Reporting and Automated Exception Ingestion:<\/strong> Ingesting runtime errors automatically from client and server-side monitoring tools (Sentry, Datadog)\u2014capturing stack traces, network payloads, breadcrumbs, and user session context without requiring manual reporting.<\/li>\n\n\n\n<li><strong>Bi-Directional Source Code and CI\/CD Integration:<\/strong> Linking bugs directly to Git branches, pull requests, and commit hashes (GitHub, GitLab, Bitbucket)\u2014automatically moving an issue to &#8220;In Review&#8221; when a PR opens, and closing it when the fix merges into the main branch.<\/li>\n\n\n\n<li><strong>Custom Workflow State-Gates and SLA Escalation:<\/strong> Enforcing strict transitions (e.g., an issue cannot jump from &#8220;Open&#8221; to &#8220;Closed&#8221; without passing through &#8220;QA Verified&#8221;), accompanied by automated SLA timers that escalate P0\/P1 blocker bugs to on-call engineering leads.<\/li>\n\n\n\n<li><strong>Cross-Functional Support and Customer Triage Links:<\/strong> Connecting bug records directly to customer support desks (Zendesk, Intercom)\u2014enabling support teams to track engineering progress without giving customer-facing staff direct access to production code backlogs.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Leading_Bug_Tracking_Tools\"><\/span>Leading Bug Tracking Tools<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Jira_Software_by_Atlassian\"><\/span>Jira Software (by Atlassian)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Jira Software<\/strong> is the global enterprise standard for issue and bug tracking, widely deployed across millions of software developers and engineering organizations. Offering unmatched workflow customization, granular permission schemes, custom field architectures, and the vast <strong>Atlassian Marketplace<\/strong>, Jira excels at managing bugs within broader Scrum, Kanban, and hybrid Agile frameworks. It pairs natively with Bitbucket, GitHub, GitLab, Confluence, and Jira Service Management.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Large software engineering departments, enterprise IT organizations, and companies requiring complex, compliance-audited workflow transitions standardize on Jira. Its primary trade-offs include administrative overhead, configuration complexity, and an interface that can feel heavy for small, fast-moving teams.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Linear\"><\/span>Linear<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Linear<\/strong> has established itself as the premier <strong>high-velocity, developer-first issue tracking platform<\/strong> for modern engineering and product teams. Built for speed, keyboard navigation, and streamlined workflows, Linear strips away administrative bloat in favor of sub-second load times, automated git workflows (auto-closing issues via PR keywords), structured cycles, and clean customer-support triage inboxes (Linear Asks).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Startups, scale-ups, and modern engineering squads who value speed, clean aesthetic design, and high developer satisfaction favor Linear over traditional enterprise issue trackers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"GitHub_Issues_and_Projects\"><\/span>GitHub Issues and Projects<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>GitHub Issues<\/strong> provides the most frictionless bug tracking experience for teams whose source code already lives on <strong>GitHub<\/strong>. Embedded directly within the repository alongside pull requests, GitHub Actions CI\/CD, and project boards, it allows developers to triage issues, cross-reference code snippets, mention team members, and automate issue states using simple markdown and automated GitHub Actions without managing a separate external tool.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Open-source projects, developer-centric startups, and engineering teams seeking zero context-switching between code reviews and bug tracking rely heavily on GitHub Issues.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"GitLab_Issue_Tracking\"><\/span>GitLab Issue Tracking<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For organizations operating on <strong>GitLab<\/strong> for their complete DevSecOps lifecycle, GitLab\u2019s built-in issue tracking, issue boards, and incident management provide a unified environment connecting defect reporting directly to security scanning, container registries, and CI\/CD deployment pipelines within a single application.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Sentry_Automated_Application_Performance_Error_Tracking\"><\/span>Sentry (Automated Application Performance &amp; Error Tracking)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">While platforms like Jira and Linear manage human-reported tasks, <strong>Sentry<\/strong> is the industry standard for <strong>automated, real-time application error and crash reporting<\/strong>. Deployed directly into application codebases across 30+ languages, Sentry catches uncaught exceptions, performance bottlenecks, and frontend crashes in real time\u2014grouping duplicate stack traces, identifying the exact commit that introduced the bug, and syncing unresolved errors directly into Jira, Linear, or GitHub Issues.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Bugzilla_and_Redmine_Self-Hosted_Open-Source_Veterans\"><\/span>Bugzilla and Redmine (Self-Hosted Open-Source Veterans)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For engineering organizations, defense contractors, or academic institutions requiring <strong>100% on-premises data ownership and zero per-seat licensing costs<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Bugzilla<\/strong> remains an established, battle-tested open-source defect tracking system known for granular search capabilities and strict state management.<\/li>\n\n\n\n<li><strong>Redmine<\/strong> provides an open-source, flexible Ruby-on-Rails issue tracker that bundles bug tracking, project wikis, Gantt charts, and forum modules for self-hosted teams.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Bug_Tracking_Tools_Comparison\"><\/span>Bug Tracking Tools Comparison<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Platform<\/strong><\/td><td><strong>Architectural Role<\/strong><\/td><td><strong>Developer Ergonomics &amp; Speed<\/strong><\/td><td><strong>Automation &amp; Source Code Sync<\/strong><\/td><td><strong>Customization &amp; Administration<\/strong><\/td><td><strong>Best Fit<\/strong><\/td><\/tr><\/thead><tbody><tr><td><strong>Jira Software<\/strong><\/td><td>Enterprise issue tracking &amp; Agile backlog platform<\/td><td>Moderate (Feature-rich, but heavier interface)<\/td><td>Very High (Deep integration with all major Git providers &amp; CI\/CD)<\/td><td>Very High (Requires dedicated admin for complex instances)<\/td><td>Enterprise engineering teams, IT organizations &amp; scaled Agile<\/td><\/tr><tr><td><strong>Linear<\/strong><\/td><td>High-velocity, developer-centric issue tracker<\/td><td>Exceptional (Keyboard-first, sub-second latency, modern UX)<\/td><td>High (Automated branch tracking, PR closing &amp; Slack triage)<\/td><td>Moderate (Opinionated, clean workflows prevent configuration sprawl)<\/td><td>Startups, scale-ups &amp; modern software engineering teams<\/td><\/tr><tr><td><strong>GitHub Issues<\/strong><\/td><td>Repo-native developer issue tracking<\/td><td>High (Native to where developers write &amp; review code)<\/td><td>Very High (Native GitHub PRs, actions, commit links &amp; branches)<\/td><td>Moderate (Configured via markdown templates &amp; GitHub Actions)<\/td><td>Developer-led teams &amp; open-source projects hosted on GitHub<\/td><\/tr><tr><td><strong>GitLab Issues<\/strong><\/td><td>DevSecOps unified issue &amp; incident tracker<\/td><td>High (Embedded inside complete DevSecOps toolchain)<\/td><td>Very High (Native GitLab CI\/CD, security scans &amp; merge requests)<\/td><td>High (Extensive enterprise security &amp; governance settings)<\/td><td>Teams running end-to-end development &amp; DevOps on GitLab<\/td><\/tr><tr><td><strong>Sentry<\/strong><\/td><td>Automated real-time error &amp; crash monitoring<\/td><td>High (Automated stack-trace capture &amp; commit tracing)<\/td><td>Very High (Captures exceptions automatically; opens issue in Jira\/Linear)<\/td><td>Moderate (SDK configuration &amp; error-grouping rules)<\/td><td>Engineering teams automating production crash and exception capture<\/td><\/tr><tr><td><strong>Bugzilla \/ Redmine<\/strong><\/td><td>Self-hosted open-source issue tracking veterans<\/td><td>Moderate\u2013Low (Traditional web interfaces, utilitarian)<\/td><td>Moderate (Git\/SVN repository linking via hooks\/plugins)<\/td><td>High (Self-hosted configuration, open-source customization)<\/td><td>Teams requiring complete on-premises data isolation with zero license cost<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Common_Bug_Tracking_Pitfalls_to_Avoid\"><\/span>Common Bug Tracking Pitfalls to Avoid<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Treating Feature Requests, User Feedback, and Systemic Bugs in the Same Backlog Without Categorization:<\/strong> Dumping raw customer suggestions into the same untagged queue as critical production crash exceptions leaves engineers overwhelmed and delays high-priority hotfixes. Maintain strict issue-type boundaries between <strong>Bugs<\/strong>, <strong>Tasks<\/strong>, and <strong>Feature Enhancements<\/strong>.<\/li>\n\n\n\n<li><strong>Failing to Automate Issue Status Changes Through Git Pull Requests:<\/strong> Forcing developers to manually open their issue tracker, search for a ticket, and drag it to &#8220;In Review&#8221; or &#8220;Done&#8221; after they already merged the pull request leads to outdated boards. Enforce git-commit keyword automation (e.g., <code>Fixes #1042<\/code>) to update ticket states automatically.<\/li>\n\n\n\n<li><strong>Neglecting to Group Automated Exception Spikes:<\/strong> Ingesting automated error feeds without smart grouping rules will flood your issue tracker with 5,000 individual tickets the moment a downstream third-party API has a brief five-minute outage. Pair crash reporting tools like Sentry with intelligent exception grouping and threshold alerts.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Selecting_the_Right_Bug_Tracking_Tool\"><\/span>Selecting the Right Bug Tracking Tool<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Match your bug tracking system to your engineering workflow, team scale, and infrastructure environment:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>For Large Enterprises Requiring Comprehensive Agile Governance and Compliance:<\/strong> Standardize on <strong>Jira Software<\/strong> for deep workflow customization and enterprise ecosystem integrations.<\/li>\n\n\n\n<li><strong>For High-Velocity Engineering Squads Prioritizing Speed and User Experience:<\/strong> Choose <strong>Linear<\/strong> for keyboard-driven workflows, clean design, and rapid sprint cycles.<\/li>\n\n\n\n<li><strong>For Repository-Native Tracking Without External Tool Overhead:<\/strong> Deploy <strong>GitHub Issues<\/strong> or <strong>GitLab Issues<\/strong> directly where your engineers manage source code and pull requests.<\/li>\n\n\n\n<li><strong>For Automating Production Crash and Exception Detection:<\/strong> Implement <strong>Sentry<\/strong> alongside your primary issue tracker to catch and diagnose code-level bugs automatically.<\/li>\n\n\n\n<li><strong>For Complete On-Premises Data Residency on Open-Source Software:<\/strong> Utilize <strong>Bugzilla<\/strong> or <strong>Redmine<\/strong>.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A software defect discovered in production is more than an inconvenience; it represents operational downtime, customer churn, and developer distraction. [&hellip;]<\/p>\n","protected":false},"author":8,"featured_media":2635,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[3128,3133,800,3131,1485,3129,3130,997,1592,3132],"class_list":["post-2627","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-bug-tracking-software","tag-defect-management","tag-devops-2","tag-github-issues","tag-gitlab","tag-issue-tracking","tag-jira-software","tag-linear","tag-sentry","tag-software-quality-assurance"],"_links":{"self":[{"href":"https:\/\/motoshare.in\/blog\/wp-json\/wp\/v2\/posts\/2627","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/motoshare.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/motoshare.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/motoshare.in\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/motoshare.in\/blog\/wp-json\/wp\/v2\/comments?post=2627"}],"version-history":[{"count":1,"href":"https:\/\/motoshare.in\/blog\/wp-json\/wp\/v2\/posts\/2627\/revisions"}],"predecessor-version":[{"id":2638,"href":"https:\/\/motoshare.in\/blog\/wp-json\/wp\/v2\/posts\/2627\/revisions\/2638"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/motoshare.in\/blog\/wp-json\/wp\/v2\/media\/2635"}],"wp:attachment":[{"href":"https:\/\/motoshare.in\/blog\/wp-json\/wp\/v2\/media?parent=2627"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/motoshare.in\/blog\/wp-json\/wp\/v2\/categories?post=2627"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/motoshare.in\/blog\/wp-json\/wp\/v2\/tags?post=2627"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}