feat: multi-server Jira integration with enhanced issue hierarchy - #9
Merged
Conversation
Add TypeScript and rimraf as devDependencies for Jira, GitLab, and Utils sources. Remove unused @types/pg from root package.json.
- Add UnprocessableError class for specific HTTP error codes - Update withRetry to break loop on UnprocessableError - Throw UnprocessableError for 400, 404, 422 status codes
…fields - Replace single-host context with multi-server architecture - Introduce `resolveCustomFields` with caching mechanism - Add support for custom fields: Epic, Planned End, Change Type, Initiative Classification - Update LLM reports to include new fields and hierarchy - Remove deprecated `getStateFromContext` utility - Refactor search to handle multiple servers and deduplicate results
Refactor Gitlab client to accept an array of Jira server configurations instead of a single host/token pair. Update types, API context, and LLM report generation to handle multiple Jira instances and a public Jira host.
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 of Changes
Main Feature: Multi-server Jira support — the codebase now supports connecting to multiple Jira servers simultaneously instead of a single server.
Key Changes:
Jira Package (
packages/sources/jira):JiraClientContextto useservers: JiraServerSettings[]array instead of singlejiraHost/jiraTokenpublicHostoption for displaying a public-facing Jira hostgetPlannedEndField,getChangeTypeField,getInitiativeClassificationField,getServers,resolveCustomFieldssearch,smartSearch,getEpicField, etc.) now iterate over all configured servers and deduplicate resultsgetPublicJiraHostfor resolving the public hostJiraIssueHierarchyItemwith:status,assignee,plannedEnd,epic,initiativeClassification,changeTypegetUserActivityto supportactorfield and improved event reportingGitLab Package (
packages/sources/gitlab):jiraServersarray instead of single host/token)Utils Package (
packages/sources/utils):UnprocessableErrorclass for non-retryable 4xx errors (400, 404, 422)withRetryto not retry onUnprocessableError@types/pgdependency