Add Jira Cloud tracker adapter#104
Merged
Merged
Conversation
Summary: - Add Jira Cloud enhanced-search polling, bulk ID refresh, and ADF normalization behind the generic tracker read boundary. - Expose host-authenticated jira_rest while stripping declared token environments from Codex children. - Add contract coverage, a real opt-in Jira E2E, and adapter docs. Rationale: - Keep Jira workflow names provider-native while preserving a small scheduler-facing read contract. - Preserve useful ADF text without inventing generic tracker writes or tenant-specific priority and blocker policy. Tests: - MIX_DEPS_PATH=/Users/frantic/code/symphony/elixir/deps make all - SYMPHONY_RUN_JIRA_LIVE_E2E=1 mix test test/symphony_elixir/jira_live_e2e_test.exs - SYMPHONY_RUN_LIVE_E2E=1 mix test test/symphony_elixir/live_e2e_test.exs:123 Co-authored-by: Codex <codex@openai.com>
Summary: - Reduce the Jira adapter notes to configuration, scoped reads, and host-authenticated tool behavior. - Keep the live test command while removing implementation narration. Rationale: - The README should explain how to use the adapter without duplicating provider implementation details or error catalogs. Tests: - git diff --check Co-authored-by: Codex <codex@openai.com>
Summary: - Preserve the landed GitHub adapter while keeping the Jira adapter branch. - Combine concise README sections, tracker registration, and coverage ignores. Rationale: - Jira must be validated and landed against the current main branch without dropping either provider. Tests: - git diff --check Co-authored-by: Codex <codex@openai.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.
Context
Symphony's generic tracker seam needs a Jira Cloud implementation without adding generic mutation APIs.
TL;DR
Add Jira Cloud reads and a host-authenticated raw Jira REST tool.
Summary
jira_restfor provider-native mutations with host-side auth.Alternatives
Test Plan
make -C elixir allSYMPHONY_RUN_JIRA_LIVE_E2E=1 mix test test/symphony_elixir/jira_live_e2e_test.exsSYMPHONY_RUN_LIVE_E2E=1 SYMPHONY_LIVE_LINEAR_TEAM_KEY=FST mix test test/symphony_elixir/live_e2e_test.exs:123