[DOCS] Jira ticket creation#11830
Conversation
✅ Deploy Preview for niobium-lead-7998 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates GX Cloud documentation to reflect Jira incident management workflows that support linking Expectation failures to new or existing Jira work items (instead of only existing Jira issues), aligning docs with DOC-1285.
Changes:
- Replaces “Jira issues” wording with “Jira work items” across cloud overview, integrations, alerts, and incidents docs.
- Expands incident-creation steps to include creating a new Jira work item from GX Cloud.
- Updates related diagrams and image alt text to match the new terminology.
Reviewed changes
Copilot reviewed 8 out of 9 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/docusaurus/static/img/alerts_incidents_actions.drawio | Updates diagram text/geometry to reflect “Jira work item” terminology. |
| docs/docusaurus/docs/cloud/overview/gx_cloud_overview.md | Updates overview copy to “new or existing Jira work items”. |
| docs/docusaurus/docs/cloud/integrations/integrations_lp.md | Updates Jira integration card description to “new or existing Jira work items”. |
| docs/docusaurus/docs/cloud/integrations/integrate_jira.md | Updates Jira integration page copy from “issues” to “work items”. |
| docs/docusaurus/docs/cloud/expectations/manage_expectations.md | Expands “Expectation history” description to include Jira work item link events. |
| docs/docusaurus/docs/cloud/alerts/responses_overview.md | Updates incidents description and image alt text to “Jira work item”. |
| docs/docusaurus/docs/cloud/alerts/manage_incidents.md | Updates incident management terminology and documents new-vs-existing work item creation flows. |
| docs/docusaurus/docs/cloud/alerts/alerts_lp.md | Updates “Manage incidents” card description to “Jira work items”. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests.
Additional details and impacted files@@ Coverage Diff @@
## develop #11830 +/- ##
============================================
- Coverage 84.67% 63.49% -21.18%
============================================
Files 471 469 -2
Lines 39179 39177 -2
============================================
- Hits 33176 24877 -8299
- Misses 6003 14300 +8297
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 8 out of 9 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 5. Select the relevant entry in the **Batches & run history** pane. | ||
| 6. Find the Expectation failure you want to unlink and click the <img src="/img/jira_logo.png" alt="jira logo" width="20" height="20"/> **Jira** icon. | ||
| 7. Find the issue you want to unlink and click <img src="/img/unlink_icon.png" alt="unlink icon" width="20" height="20"/> **Unlink issue**. | ||
| 7. Find the work item you want to unlink and click <img src="/img/unlink_icon.png" alt="unlink icon" width="20" height="20"/> **Unlink work item**. |
There was a problem hiding this comment.
@dctalbot I think the hovers on the link and unlink buttons still say "link issue" and "unlink issue". Can we update?
|
Is this PR still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions 🙇 |
resolves https://greatexpectations.atlassian.net/browse/DOC-1285 according to the plan linked in that issue
invoke lint(usesruff format+ruff check)For more information about contributing, visit our community resources.
After you submit your PR, keep the page open and monitor the statuses of the various checks made by our continuous integration process at the bottom of the page. Please fix any issues that come up and reach out on Slack if you need help. Thanks for contributing!