added a new section for Figma page loading issues#862
Conversation
WalkthroughNormalized many troubleshooting page front-matter Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (7)
src/pages/docs/troubleshooting/web-apps/url-not-accessible.md (1)
6-6: Duplicate concern: Page ID standardization (see recorder-failed.md review).src/pages/docs/troubleshooting/web-apps/page-loading-issues.md (1)
6-6: Duplicate concern: Page ID standardization (see recorder-failed.md review).src/pages/docs/troubleshooting/on-prem/restart-docker.md (1)
6-6: Duplicate concern: Page ID standardization (see recorder-failed.md review).src/pages/docs/troubleshooting/agent/fix-agent-registration-failures.md (1)
7-7: Duplicate concern: Page ID standardization (see recorder-failed.md review).src/pages/docs/troubleshooting/REST-API/troubleshooting-api-testcase-failure.md (1)
6-6: Duplicate concern: Page ID standardization (see recorder-failed.md review).src/pages/docs/troubleshooting/agent/agent-cleanup.md (1)
7-7: Duplicate concern: Page ID standardization (see recorder-failed.md review).src/pages/docs/troubleshooting/web-apps/chrome-settings.md (1)
6-6: Duplicate concern: Page ID standardization (see recorder-failed.md review).
🧹 Nitpick comments (1)
src/pages/docs/atto/generative-ai/generate-tests/requirements.md (1)
85-111: Consider formatting consistency with other sections.The troubleshooting content uses a blockquote with an HTML
<p>tag for the heading, while other major sections (Jira, QTest, Video, Files) use markdown heading syntax (## **Section Name**). For consistency and better semantic structure, consider reformatting this section to match the document's heading convention.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (37)
src/pages/docs/atto/generative-ai/generate-tests/requirements.md(1 hunks)src/pages/docs/troubleshooting/NLPs/drag-and-drop.md(1 hunks)src/pages/docs/troubleshooting/NLPs/mysql-db-test-cases.md(1 hunks)src/pages/docs/troubleshooting/NLPs/need-for-clearing-cookies.md(1 hunks)src/pages/docs/troubleshooting/NLPs/ui-identifier.md(1 hunks)src/pages/docs/troubleshooting/NLPs/unable-to-capture-dropdown-element.md(1 hunks)src/pages/docs/troubleshooting/NLPs/unable-to-click-checkbox.md(1 hunks)src/pages/docs/troubleshooting/NLPs/unable-to-retrieve-value.md(1 hunks)src/pages/docs/troubleshooting/NLPs/unable-to-select-radiobutton.md(1 hunks)src/pages/docs/troubleshooting/NLPs/upload-files.md(1 hunks)src/pages/docs/troubleshooting/REST-API/troubleshooting-api-testcase-failure.md(1 hunks)src/pages/docs/troubleshooting/agent/agent-cleanup.md(1 hunks)src/pages/docs/troubleshooting/agent/agent-failures-due-to-used-ports.md(1 hunks)src/pages/docs/troubleshooting/agent/fix-agent-registration-failures.md(1 hunks)src/pages/docs/troubleshooting/agent/local-tests-queued.md(1 hunks)src/pages/docs/troubleshooting/agent/need-of-apache-tomcat-agent.md(1 hunks)src/pages/docs/troubleshooting/agent/unable-to-create-new-testsession.md(1 hunks)src/pages/docs/troubleshooting/desktop-windows/recorder-failed.md(1 hunks)src/pages/docs/troubleshooting/general/automating-chrome-extension.md(1 hunks)src/pages/docs/troubleshooting/general/enable-disable-elements.md(1 hunks)src/pages/docs/troubleshooting/general/figma-pages-not-loading-in-testsigma.md(0 hunks)src/pages/docs/troubleshooting/general/jenkins-xml-to-html.md(1 hunks)src/pages/docs/troubleshooting/general/ui-elements-for-ios-apps.md(1 hunks)src/pages/docs/troubleshooting/general/verify-file-download.md(1 hunks)src/pages/docs/troubleshooting/general/view-test-execution-video.md(1 hunks)src/pages/docs/troubleshooting/on-prem/general-issues.md(1 hunks)src/pages/docs/troubleshooting/on-prem/restart-docker.md(1 hunks)src/pages/docs/troubleshooting/setup/secured-business-application-support.md(1 hunks)src/pages/docs/troubleshooting/setup/server-docker-deployment-errors.md(1 hunks)src/pages/docs/troubleshooting/setup/troubleshooting-restricted-access.md(1 hunks)src/pages/docs/troubleshooting/web-apps/chrome-settings.md(1 hunks)src/pages/docs/troubleshooting/web-apps/collecting-har-file.md(1 hunks)src/pages/docs/troubleshooting/web-apps/issues-with-browser-sessions.md(1 hunks)src/pages/docs/troubleshooting/web-apps/issues-with-ui-Identifiers.md(1 hunks)src/pages/docs/troubleshooting/web-apps/page-loading-issues.md(1 hunks)src/pages/docs/troubleshooting/web-apps/test-execution-queued-for-a-long-time.md(1 hunks)src/pages/docs/troubleshooting/web-apps/url-not-accessible.md(1 hunks)
💤 Files with no reviewable changes (1)
- src/pages/docs/troubleshooting/general/figma-pages-not-loading-in-testsigma.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: CI
🔇 Additional comments (26)
src/pages/docs/troubleshooting/agent/unable-to-create-new-testsession.md (1)
6-6: No changes needed. Thepage_idformat is already standardized across all troubleshooting documentation and follows the established kebab-case lowercase convention used consistently throughout the codebase. The change poses no risk to documentation functionality or routing.src/pages/docs/troubleshooting/setup/troubleshooting-restricted-access.md (1)
6-6: No action required — page_id is documentation metadata only.The page_id change to kebab-case format is safe. Navigation and routing in the codebase use URL paths (defined in
left-nav-title.json), not page_id values. This is a metadata-only change with no risk of breaking internal links or systems.Likely an incorrect or invalid review comment.
src/pages/docs/troubleshooting/web-apps/issues-with-ui-Identifiers.md (2)
1-32: Clarify PR scope: mismatch between objectives and file content.The PR objectives mention "added a new section for Figma page loading issues," but the provided file is about UI Identifiers troubleshooting. This appears to be a metadata standardization change (page_id normalization) rather than new Figma content.
Please clarify whether:
- Only a subset of changed files was provided for review
- Multiple unrelated changes were bundled into this PR
- The PR objectives accurately reflect all changes being made
6-6: Remove unnecessary verification request—this is a safe metadata standardization.The page_id change from title-case to kebab-case is a non-breaking metadata update. The page_id field is not used for routing, URL generation, or navigation in the Gatsby configuration, and no hardcoded references to the old value exist in the codebase. This change aligns with the kebab-case standardization already in use across other troubleshooting and visual-testing documentation files.
src/pages/docs/troubleshooting/setup/secured-business-application-support.md (2)
1-14: Note: PR objectives and actual file content appear misaligned.The PR title mentions "added a new section for Figma page loading issues," but the file reviewed is a troubleshooting guide for secured business applications with only a front matter metadata change. This suggests either the file list provided is incomplete or the PR scope is broader than shown. Verify that all changed files have been included in this review, especially if Figma-related content changes are part of this PR.
6-6: No action needed — page_id field is not used in the build system.The
page_idfield in the front matter is metadata that is not queried or consumed by gatsby-node.js during page generation. The graphql query in gatsby-node.js explicitly excludespage_id, using onlytitle,metadesc,canonical,keywords, and other SEO fields. Routing and navigation are based on the file slug, notpage_id, so this change poses no risk of breaking references.src/pages/docs/atto/generative-ai/generate-tests/requirements.md (1)
78-78: Content relocation improves readability.Moving the "Clear Selection" bullet after the image provides better visual flow and allows readers to understand the UI before learning about the action.
src/pages/docs/troubleshooting/general/view-test-execution-video.md (1)
7-7: Thepage_idfield change has no functional impact on routing, navigation, or search indexing.This is a safe metadata normalization. The codebase analysis shows that
page_idis not used for URL routing (which relies onslugfrom Gatsby), search indexing (which indexestitle,search_keyword,slug,excerpt, andheadingsvia Typesense), or navigation configuration. The field appears to be unused metadata, so normalizing it from title-case to kebab-case poses no risk of breaking links, routing, or search functionality.Likely an incorrect or invalid review comment.
src/pages/docs/troubleshooting/agent/need-of-apache-tomcat-agent.md (1)
7-7: Metadata normalization consistent with other files.The page_id change aligns with the broader kebab-case standardization across the troubleshooting documentation.
src/pages/docs/troubleshooting/general/automating-chrome-extension.md (1)
6-6: Metadata normalization consistent.The kebab-case standardization is applied consistently.
src/pages/docs/troubleshooting/NLPs/need-for-clearing-cookies.md (1)
6-6: Metadata normalization applied consistently.The change follows the documentation standardization pattern.
src/pages/docs/troubleshooting/on-prem/general-issues.md (1)
4-4: Improved page identifier clarity.The updated page_id includes "on-prem" context, which makes the identifier more specific and less ambiguous. This is a good improvement alongside the normalization.
src/pages/docs/troubleshooting/NLPs/unable-to-retrieve-value.md (1)
6-6: Metadata normalization applied.The change maintains consistency with the documentation standardization effort.
src/pages/docs/troubleshooting/NLPs/ui-identifier.md (1)
6-6: Metadata normalization applied.The change maintains consistency with the documentation standardization effort.
src/pages/docs/troubleshooting/web-apps/collecting-har-file.md (1)
6-6: Metadata normalization applied.The change maintains consistency with the documentation standardization effort.
src/pages/docs/troubleshooting/web-apps/issues-with-browser-sessions.md (1)
6-6: No action needed. Thepage_idfield is front matter metadata that is not used by the Gatsby build process for routing, navigation, or link generation. Changes topage_idvalues have no impact on site functionality or external references.src/pages/docs/troubleshooting/NLPs/mysql-db-test-cases.md (1)
6-6: Verify no breaking changes from page_id standardization.This page_id change follows the kebab-case standardization pattern, but any external systems, routing configurations, or internal documentation links that reference the old page_id
"Use MySQL Addon in NLPs"will break. Ensure all references have been updated.src/pages/docs/troubleshooting/NLPs/upload-files.md (1)
6-6: Verify no breaking changes from page_id standardization.The page_id has been converted to kebab-case. Ensure all routing, internal links, or external API references pointing to
"Uploading Files NLP"have been updated to"uploading-files-nlp".src/pages/docs/troubleshooting/NLPs/unable-to-click-checkbox.md (1)
6-6: Verify no breaking changes from page_id standardization.Ensure any references to the old page_id
"Unable to Click Checkbox"have been updated throughout the documentation system and any dependent services.src/pages/docs/troubleshooting/web-apps/test-execution-queued-for-a-long-time.md (1)
6-6: Verify no breaking changes and confirm slug truncation is intentional.The page_id has been significantly condensed from a verbose title to
"troubleshooting-test-execution-state-is-queued-for-long". Confirm this slug length/truncation is intentional and consistent with the project's naming conventions. Additionally, ensure all references to the old page_id have been updated.src/pages/docs/troubleshooting/general/jenkins-xml-to-html.md (1)
6-6: Verify no breaking changes from page_id standardization.The page_id has been converted to kebab-case. Ensure all dependencies (routing, internal links, external APIs) referencing
"Convert JUnit XML Report to HTML"have been updated.src/pages/docs/troubleshooting/agent/local-tests-queued.md (1)
7-7: Verify slug consistency and breaking changes.The page_id now reads
"permanently-queued-in-local-executions"(dropping "Tests" from the beginning). Ensure this slug naming approach is consistent with other pages in the PR. Also verify all references to the old page_id"Tests Permanently Queued in Local executions"have been updated.src/pages/docs/troubleshooting/NLPs/drag-and-drop.md (1)
6-6: Verify no breaking changes from page_id standardization.The ampersand (
&) has been replaced with a hyphen in the kebab-case conversion. Ensure all references to"Drag & Drop NLP"have been updated to the new format.src/pages/docs/troubleshooting/general/verify-file-download.md (1)
7-7: Verify no breaking changes from page_id standardization.The forward slash has been removed in the kebab-case conversion, and the slug now reads
"verify-file-download". Ensure all references to the old page_id"Verify/Confirm File Download"have been updated.src/pages/docs/troubleshooting/desktop-windows/recorder-failed.md (1)
7-7: page_id is unused metadata and change is safe.The
page_idfield is not used by Gatsby for URL routing or any other functionality. URL routing is based on file paths viacreateFilePath, not frontmatter fields. This metadata-only change carries no risk of breaking existing links or requiring redirects.src/pages/docs/troubleshooting/agent/agent-failures-due-to-used-ports.md (1)
7-7: Verify page_id change doesn't break routing or external references.The
page_idis being normalized to lowercase kebab-case. If this identifier is used for routing, sitemap generation, SEO, or internal documentation links, confirm that redirects are in place and that external bookmarks/links won't break.
|
|
||
| > <p id="prerequisites">Troubleshooting: Figma Pages Not Loading in Testsigma</p> | ||
| > | ||
| > | ||
| > In some cases, the Figma pages may fail to load and display **No pages** even if the same file worked previously. This issue typically occurs when Figma’s API rate limits are exceeded, preventing Testsigma from fetching the required page data. | ||
| > | ||
| >  | ||
| > | ||
| > ### **Cause** | ||
| > | ||
| > This issue occurs because Figma has recently tightened its API rate limits, which restrict how frequently external tools can request data. When these limits are exceeded, Figma temporarily stops returning page information, so Testsigma cannot load the list of pages and shows **No pages**. This happens more often with accounts with lower access such as **Viewer**, as they hit the reduced limits much faster. | ||
| > | ||
| > | ||
| > ### **Steps to Resolve the Issue** | ||
| > | ||
| > **1. Verify the Figma API Key Permissions** <br> | ||
| > Ensure the API key used in Testsigma belongs to a Figma account with a **Dev/Full seat**. These roles provide higher API rate limits and help prevent intermittent failures. | ||
| > | ||
| > **2. Re-generate the API Key (If Needed)** <br> | ||
| > If the current key was created under a seat with restricted API access, generate a new key from an account with a higher access tier. | ||
| > | ||
| > **3. Wait for Rate Limits to Reset** <br> | ||
| > If rate limits were exceeded, Figma may temporarily block further requests. Wait a few minutes and then try loading the pages again. | ||
| > | ||
| > **4. Review Figma Rate Limits** <br> | ||
| > For detailed info on rate limits, see [Figma’s Rate Limits](https://developers.figma.com/docs/rest-api/rate-limits/). | ||
|
|
There was a problem hiding this comment.
Fix duplicate ID in troubleshooting section heading.
Line 86 uses id="prerequisites", which duplicates the ID already defined on line 39. This creates invalid markup and breaks anchor linking. Use a unique, descriptive ID for this troubleshooting section instead.
Apply this diff to fix the duplicate ID:
- > <p id="prerequisites">Troubleshooting: Figma Pages Not Loading in Testsigma</p>
+ > <p id="troubleshooting-figma-pages-not-loading">Troubleshooting: Figma Pages Not Loading in Testsigma</p>Additionally, update the contextual links at the top of the file to include an entry for this new section so it appears in the table of contents:
- type: link
name: "Add the Data from Files"
url: "#add-the-data-from-files"
+ - type: link
+ name: "Troubleshooting: Figma Pages Not Loading"
+ url: "#troubleshooting-figma-pages-not-loading"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| > <p id="prerequisites">Troubleshooting: Figma Pages Not Loading in Testsigma</p> | |
| > | |
| > | |
| > In some cases, the Figma pages may fail to load and display **No pages** even if the same file worked previously. This issue typically occurs when Figma’s API rate limits are exceeded, preventing Testsigma from fetching the required page data. | |
| > | |
| >  | |
| > | |
| > ### **Cause** | |
| > | |
| > This issue occurs because Figma has recently tightened its API rate limits, which restrict how frequently external tools can request data. When these limits are exceeded, Figma temporarily stops returning page information, so Testsigma cannot load the list of pages and shows **No pages**. This happens more often with accounts with lower access such as **Viewer**, as they hit the reduced limits much faster. | |
| > | |
| > | |
| > ### **Steps to Resolve the Issue** | |
| > | |
| > **1. Verify the Figma API Key Permissions** <br> | |
| > Ensure the API key used in Testsigma belongs to a Figma account with a **Dev/Full seat**. These roles provide higher API rate limits and help prevent intermittent failures. | |
| > | |
| > **2. Re-generate the API Key (If Needed)** <br> | |
| > If the current key was created under a seat with restricted API access, generate a new key from an account with a higher access tier. | |
| > | |
| > **3. Wait for Rate Limits to Reset** <br> | |
| > If rate limits were exceeded, Figma may temporarily block further requests. Wait a few minutes and then try loading the pages again. | |
| > | |
| > **4. Review Figma Rate Limits** <br> | |
| > For detailed info on rate limits, see [Figma’s Rate Limits](https://developers.figma.com/docs/rest-api/rate-limits/). | |
| > <p id="troubleshooting-figma-pages-not-loading">Troubleshooting: Figma Pages Not Loading in Testsigma</p> | |
| > | |
| > | |
| > In some cases, the Figma pages may fail to load and display **No pages** even if the same file worked previously. This issue typically occurs when Figma's API rate limits are exceeded, preventing Testsigma from fetching the required page data. | |
| > | |
| >  | |
| > | |
| > ### **Cause** | |
| > | |
| > This issue occurs because Figma has recently tightened its API rate limits, which restrict how frequently external tools can request data. When these limits are exceeded, Figma temporarily stops returning page information, so Testsigma cannot load the list of pages and shows **No pages**. This happens more often with accounts with lower access such as **Viewer**, as they hit the reduced limits much faster. | |
| > | |
| > | |
| > ### **Steps to Resolve the Issue** | |
| > | |
| > **1. Verify the Figma API Key Permissions** <br> | |
| > Ensure the API key used in Testsigma belongs to a Figma account with a **Dev/Full seat**. These roles provide higher API rate limits and help prevent intermittent failures. | |
| > | |
| > **2. Re-generate the API Key (If Needed)** <br> | |
| > If the current key was created under a seat with restricted API access, generate a new key from an account with a higher access tier. | |
| > | |
| > **3. Wait for Rate Limits to Reset** <br> | |
| > If rate limits were exceeded, Figma may temporarily block further requests. Wait a few minutes and then try loading the pages again. | |
| > | |
| > **4. Review Figma Rate Limits** <br> | |
| > For detailed info on rate limits, see [Figma's Rate Limits](https://developers.figma.com/docs/rest-api/rate-limits/). |
🤖 Prompt for AI Agents
In src/pages/docs/atto/generative-ai/generate-tests/requirements.md around lines
85 to 111, the troubleshooting heading uses a duplicate id="prerequisites"
(already used at line 39); update the heading to a unique, descriptive id such
as id="figma-no-pages-troubleshooting" (or similar) and then add a corresponding
entry/link to that new id in the file’s table of contents / contextual links at
the top so the anchor works and markup is valid.
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/left-nav-title.json(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: CI
| "jira": {"/docs/integrations/bug-reporting/jira/": "Jira" }, | ||
| "jira": {"/docs/atto/generative-ai/integrations/jira/": "Jira"}, | ||
| "xray": {"/docs/atto/generative-ai/integrations/xray/": "Xray"}, | ||
| "qtest": {"/docs/atto/generative-ai/integrations/qtest/": "qTest" } |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, let's check if the file exists and its size
ls -lh src/left-nav-title.json && wc -l src/left-nav-title.jsonRepository: testsigmahq/testsigma-docs
Length of output: 169
🏁 Script executed:
# Read the specific lines mentioned in the review
echo "=== Lines 757-760 (disputed section) ===" && sed -n '757,760p' src/left-nav-title.json
echo ""
echo "=== Lines 423 (claimed earlier jira) ===" && sed -n '423p' src/left-nav-title.json
echo ""
echo "=== Lines 729-732 (claimed earlier entries) ===" && sed -n '729,732p' src/left-nav-title.jsonRepository: testsigmahq/testsigma-docs
Length of output: 754
🏁 Script executed:
# Let's see more context around these sections to understand the structure
echo "=== Context around lines 755-765 ===" && sed -n '755,765p' src/left-nav-title.json
echo ""
echo "=== Context around lines 420-430 ===" && sed -n '420,430p' src/left-nav-title.json
echo ""
echo "=== Context around lines 725-735 ===" && sed -n '725,735p' src/left-nav-title.jsonRepository: testsigmahq/testsigma-docs
Length of output: 1738
🏁 Script executed:
# Let's understand the parent structure
echo "=== Broader context (lines 410-435) ===" && sed -n '410,435p' src/left-nav-title.json
echo ""
echo "=== Broader context (lines 720-765) ===" && sed -n '720,765p' src/left-nav-title.jsonRepository: testsigmahq/testsigma-docs
Length of output: 4407
🏁 Script executed:
# Validate if the JSON is well-formed and check for parent structure
jq . src/left-nav-title.json > /dev/null 2>&1 && echo "JSON is valid" || echo "JSON is invalid"
# Find the parent key that contains these duplicate keys
jq 'keys' src/left-nav-title.json | head -20Repository: testsigmahq/testsigma-docs
Length of output: 546
🏁 Script executed:
# Check if there are duplicate keys at top level
jq 'keys' src/left-nav-title.json | jq -r '.[]' | sort | uniq -d | head -20
# Also check the entire JSON structure to find where the duplicates are
echo "=== Looking for parent object around line 720 ===" && sed -n '700,730p' src/left-nav-title.json | head -40Repository: testsigmahq/testsigma-docs
Length of output: 2794
🏁 Script executed:
# Count occurrences of potentially duplicate keys at the same level
echo "=== Counting occurrences of keys ==="
rg '"jira":\s*\{' src/left-nav-title.json | wc -l
rg '"xray":\s*\{' src/left-nav-title.json | wc -l
rg '"qtest":\s*\{' src/left-nav-title.json | wc -l
rg '"live-editor":\s*\{' src/left-nav-title.json | wc -l
rg '"requirements":\s*\{' src/left-nav-title.json | wc -l
# Also show all lines with these keys
echo ""
echo "=== All 'jira' entries ===" && rg -n '"jira":\s*\{' src/left-nav-title.jsonRepository: testsigmahq/testsigma-docs
Length of output: 369
🏁 Script executed:
# Let's verify what jq actually keeps (last occurrence)
echo "=== What jq preserves for 'jira' ===" && jq '.jira' src/left-nav-title.json
echo ""
echo "=== What jq preserves for 'xray' ===" && jq '.xray' src/left-nav-title.json
echo ""
echo "=== What jq preserves for 'qtest' ===" && jq '.qtest' src/left-nav-title.json
# Show all occurrences of xray to see the overwriting
echo ""
echo "=== All 'xray' entries ===" && rg -n '"xray":\s*\{' src/left-nav-title.json
echo ""
echo "=== All 'qtest' entries ===" && rg -n '"qtest":\s*\{' src/left-nav-title.jsonRepository: testsigmahq/testsigma-docs
Length of output: 1006
Critical: Duplicate JSON keys cause silent data loss.
The file contains duplicate top-level keys ("jira", "xray", "qtest") appearing 4–5 times each. JSON parsers retain only the last occurrence, permanently discarding earlier mappings:
- Line 423
"jira"(bug-reporting) → lost, overwritten by line 758 - Line 426
"xray"(bug-reporting) → lost, overwritten by line 759 - Line 699
"xray"(test-management) → lost, overwritten by line 759 - Line 700
"qtest"(test-management) → lost, overwritten by line 760
Only the final entries (lines 758–760, all pointing to atto/generative-ai paths) are retained. All bug-reporting and test-management navigation mappings are silently discarded.
Remove lines 757–760, or consolidate duplicate keys by renaming them (e.g., "jira-atto", "jira-bug-reporting") if all mappings must coexist.
🤖 Prompt for AI Agents
In src/left-nav-title.json around lines 757 to 760 there are duplicate top-level
keys ("jira", "xray", "qtest") that overwrite earlier entries and cause silent
data loss; remove the duplicate block at 757–760 or consolidate by renaming keys
so all mappings coexist (e.g., "jira-bug-reporting" vs "jira-atto" or merge the
paths under a single unique key), and ensure the final JSON has unique keys for
each navigation mapping and validates as proper JSON.
* Updated Jira Bug Reporting doc (#858) * Created new doc Figma page Loading issues (#859) * Added a new section to docs (#860) * Added a new section to docs * Update live-editor.md * Update using-auto-healing-in-live-editor-test-execution.md * Update unable-to-download-the-packages-required-to-start-the-agent.md * Updated Testsigma Terminal docs and added a new section (#861) * Added a new section * Update unable-to-start-the-terminal-due-to-port-unavailability.md * added a new section for Figma page loading issues (#862) * added a new section for Figma page loading issues * Update left-nav-title.json * updated requirement doc (#863) * Added a new doc 'Configure User & Org Settings' (#864) Added a new doc 'Configure User & Org Settings' * updated Components of Testsigma Terminal doc (#865) * Deleted 'Configure User & Organization Settings' (#867) --------- Co-authored-by: Bharath Krishna <118433150+bharathk08@users.noreply.github.com>
2 participants
added a new section for Figma page loading issues
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.