Skip to content

chore: update compass.yml — Jira board, status page, tier, lifecycle and metadata [PYSDK-82] - #570

Merged
helmut-hoffer-von-ankershoffen merged 4 commits into
mainfrom
chore/PYSDK-82-compass-links
Apr 24, 2026
Merged

chore: update compass.yml — Jira board, status page, tier, lifecycle and metadata [PYSDK-82]#570
helmut-hoffer-von-ankershoffen merged 4 commits into
mainfrom
chore/PYSDK-82-compass-links

Conversation

@helmut-hoffer-von-ankershoffen

@helmut-hoffer-von-ankershoffenhelmut-hoffer-von-ankershoffen commented Apr 24, 2026

Copy link
Copy Markdown
Contributor

🛡️ Implements PYSDK-82 following CC-SOP-01 Change Control, part of our ISO 13485-certified QMS | Ketryx Project

Summary

  • Add Jira board link (PROJECT_TRACKER) pointing to the PYSDK board in Compass
  • Add BetterStack status page link (STATUS_PAGE) pointing to status.aignostics.com
  • Set tier to 1, lifecycle to Active, isMonorepoProject to false
  • Populate previously empty custom fields: Component Key, Deployment Branch, Development Branch, Has external API/CLI/GUI, Is independently deployable, Is open source, Path in Repository

Why

Enriches the Compass component catalog entry so the Python SDK is correctly classified, linked to its operational resources, and visible to on-call and platform teams.

Test plan

  • Verify Compass component page shows Jira board and status page links after merge
  • Verify tier and lifecycle fields are reflected in Compass

🤖 Generated with Claude Code

CopilotAI review requested due to automatic review settings April 24, 2026 14:10
@helmut-hoffer-von-ankershoffenhelmut-hoffer-von-ankershoffen added the skip:test:long_running Skip long-running tests (≥5min) label Apr 24, 2026

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Atlassian Compass component definition for the Python SDK to enrich operational and ownership metadata (Jira board, status page, tier/lifecycle, and custom field population).

Changes:

  • Added Compass links for the PYSDK Jira board and BetterStack status page.
  • Updated component classification fields (tier, lifecycle, monorepo flag).
  • Filled in previously empty Compass custom fields (component key, branches, external interfaces, deployability, repo path).

Comment threadcompass.yml
- name: Deployment Branch
type: text
value: null
value: release/*

CopilotAIApr 24, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Deployment Branch" is set to release/*, but this repo consistently uses the release/v* naming pattern for release branches (e.g., .github/workflows/ci-cd.yml triggers on release/v*, and CONTRIBUTING.md documents release/vX.Y.Z). Consider updating this value to release/v* to match the established convention.

Suggested change
value: release/*
value: release/v*

Copilot uses AI. Check for mistakes.
Comment threadcompass.yml
Comment on lines +17 to +19
- name: Jira Board
type: PROJECT_TRACKER
url: https://aignx.atlassian.net/jira/software/projects/PYSDK/boards

CopilotAIApr 24, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR description says this link should point to the PYSDK Jira board, but the URL ends at /boards (board list) rather than a specific board (typically /boards/<boardId>). If the intent is a direct board link, update the URL to the concrete board URL so Compass users land on the intended board immediately.

Copilot uses AI. Check for mistakes.
Comment threadcompass.yml
value: false
value: true
- name: Is open source
type: true

CopilotAIApr 24, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The custom field "Is open source" is malformed: it sets type: true (should be a valid Compass field type like boolean) and it doesn't provide a value. This will likely make the compass.yml invalid for Compass ingestion. Set type: boolean and add an explicit value: true/false (and keep the schema consistent with other boolean custom fields above).

Suggested change
type: true
type: boolean
value: true

Copilot uses AI. Check for mistakes.
@codecov

codecovBot commented Apr 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

❗ There is a different number of reports uploaded between BASE (62aa11f) and HEAD (1ab1dd4). Click for more details.

HEAD has 2 uploads less than BASE
FlagBASE (62aa11f)HEAD (1ab1dd4)
31

see 22 files with indirect coverage changes

@sonarqubecloud

Copy link
Copy Markdown

@helmut-hoffer-von-ankershoffen
helmut-hoffer-von-ankershoffen marked this pull request as ready for review April 24, 2026 15:34
CopilotAI review requested due to automatic review settings April 24, 2026 15:34
@claude

claudeBot commented Apr 24, 2026

Copy link
Copy Markdown

Claude finished @helmut-hoffer-von-ankershoffen's task in 2m 48s —— View job


Review Complete: PR #570 Compass Configuration Updates

Todo List:

  • Read CLAUDE.md files to understand repository conventions
  • Review compass.yml changes
  • Verify Copilot's identified issues
  • Check for additional issues
  • Provide comprehensive review feedback

Review Summary

I've reviewed the Compass configuration changes and confirmed 3 blocking issues that must be fixed before merge. All issues were correctly identified by Copilot and verified against repository conventions.


🚨 BLOCKING ISSUES

1. Incorrect Deployment Branch Pattern (Line 54)

Issue: The deployment branch is set to release/* but this repository consistently uses release/v* pattern.

Evidence from repository:

  • .github/workflows/ci-cd.yml triggers on release/v*
  • .github/workflows/merge-release.yml validates release/vX.Y.Z pattern
  • CLAUDE.md and CONTRIBUTING.md document release/vX.Y.Z branches
  • Example: release/v1.2.3

Location: compass.yml:54

Current:

 - name: Deployment Branchtype: textvalue: release/*

Fix:

 - name: Deployment Branchtype: textvalue: release/v*

2. Jira Board URL Points to Board List (Line 19)

Issue: The URL points to the PYSDK project's board listing page instead of a specific board.

Location: compass.yml:19

Current:

 - name: Jira Boardtype: PROJECT_TRACKERurl: https://aignx.atlassian.net/jira/software/projects/PYSDK/boards

Expected: A direct link to the specific board (e.g., https://aignx.atlassian.net/jira/software/c/projects/PYSDK/boards/123)

Recommendation: Update to the specific board URL so users land directly on the PYSDK board, not the board list.


3. Malformed "Is open source" Custom Field (Lines 82-83)

Issue: The custom field has incorrect structure:

  • type: true (should be type: boolean)
  • Missing value field

Location: compass.yml:82-83

Current:

 - name: Is open sourcetype: true

Fix (confirmed by LICENSE file - MIT license means it IS open source):

 - name: Is open sourcetype: booleanvalue: true

Pattern verification: All other boolean fields in this file follow this exact structure (e.g., "Has external API", "CSV Approved").


✅ POSITIVE FINDINGS

  • YAML syntax is valid (parseable)
  • Tier upgrade (4 → 1) correctly reflects importance of this SDK
  • Lifecycle status (Active) is appropriate
  • Status page URL format looks correct
  • All other metadata fields are correctly populated
  • Good addition of operational links for on-call visibility

📋 ACTION ITEMS FOR AUTHOR

To fix all blocking issues:

  1. Line 54: Change value: release/*value: release/v*
  2. Line 19: Update with specific board URL (check Jira for the exact board ID)
  3. Lines 82-83: Replace with:
     - name: Is open sourcetype: booleanvalue: true

Verify the fix:

# Validate YAML syntax
uv run python -c "import yaml; yaml.safe_load(open('compass.yml'))"# Verify all boolean fields have correct structure
uv run python -c "import yaml, json; data = yaml.safe_load(open('compass.yml')); bools = [f for f in data['customFields'] if isinstance(f.get('type'), str) and f['type'] == 'boolean']; print(f'Found {len(bools)} boolean fields, all correctly structured')"

📚 References

  • Branch naming conventions: .github/CLAUDE.md, CLAUDE.md (Version Bumping and Releases section)
  • Compass field patterns: Existing boolean fields in compass.yml
  • Open source status: LICENSE file (MIT License)

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Comment threadcompass.yml
value: false
value: true
- name: Is open source
type: true

CopilotAIApr 24, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The newly added custom field "Is open source" is malformed: it sets type: true (a boolean) and provides no value. This will likely fail Compass schema validation. Set type to the expected field type (e.g., boolean) and add an explicit value (true/false).

Suggested change
type: true
type: boolean
value: true

Copilot uses AI. Check for mistakes.
@helmut-hoffer-von-ankershoffen
helmut-hoffer-von-ankershoffen merged commit 1fd4536 into mainApr 24, 2026
31 of 32 checks passed
@helmut-hoffer-von-ankershoffen
helmut-hoffer-von-ankershoffen deleted the chore/PYSDK-82-compass-links branch April 24, 2026 15:37
@helmut-hoffer-von-ankershoffenhelmut-hoffer-von-ankershoffen added sop:cc-sop-01 CC-SOP-01 Change Control (feature / planned change) type:chore Tooling, maintenance, routine task (conventional chore) scope:dev-only Affects only our dev/CI env; consumers unaffected labels Apr 24, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

scope:dev-onlyAffects only our dev/CI env; consumers unaffectedskip:test:long_runningSkip long-running tests (≥5min)sop:cc-sop-01CC-SOP-01 Change Control (feature / planned change)type:choreTooling, maintenance, routine task (conventional chore)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@helmut-hoffer-von-ankershoffen