KAN-743: Migrate issue tracking to Jira (docs-pro) - #23
Open
sundayonah wants to merge 4 commits into
Open
Conversation
…ccuracy Enhance the documentation for the GET /v2/markets endpoint by refining descriptions of query filters and response structures. Ensure consistency with recent API changes, including the addition of optional parameters and improved examples. This update aims to provide clearer guidance for developers integrating with the markets API.
Refine the issue templates for bug reports and feature requests by removing outdated title and label fields, emphasizing that issues are tracked in Jira (project KAN). Additionally, enhance the README to include a note for Paycrest team members to file engineering work in Jira with the appropriate label. This update aims to streamline the issue reporting process and improve documentation clarity.
…ocks) Co-authored-by: Cursor <cursoragent@cursor.com>
…ue templates Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pilot migration of issue/ticket creation from GitHub Issues to Jira project KAN for the docs repo (
docs-pro), per KAN-743.Add `AGENTS.md` and `docs/agents/issue-tracker.md` (Jira KAN, label `repo-docs-pro`, Atlassian MCP, Bug/Task mapping, PR linking)
Replace issue templates with redirect to the KAN board (Issues tab stays enabled)
Add PR template `Jira Issue:` line
Update `config.yaml` with Jira KAN contact link
What does NOT change
Jira Issue
Jira Issue: https://paycrest-io.atlassian.net/browse/KAN-743
Test plan