Jira plugin support

[ewega]

Summary

Add Jira as a supported DevOps tool in the CLI. Jira is the most popular issue tracker globally (~75% enterprise adoption), providing change lead time and issue resolution data for DORA metrics.

Upstream Plugin

jira in incubator-devlake/backend/plugins/jira/

Property	Value
Plugin slug	jira
Auth	MultiAuth (AccessToken for Jira Cloud, BasicAuth for Jira Server)
Scope type	Boards (BoardId uint64)
Scope ID field	boardId
Default endpoint	User-provided (e.g., https://your-domain.atlassian.net/)
Remote-scope API	Yes
Connection test	Yes

Dependencies

Blocked by:

• Generalize auth model for multi-plugin support #85 — Auth generalization (Jira Cloud uses AccessToken, Jira Server uses BasicAuth)
• Generic scope ID extraction and remote-scope API client #86 — Scope ID extraction (boardId is uint64, not in current ScopeListEntry)

Changes

• Add ConnectionDef for jira in connectionRegistry:
  • AuthMethod: "AccessToken" (Jira Cloud; BasicAuth for Server can be added later)
  • Endpoint: "" (user must provide)
  • SupportsTest: true
  • TokenPrompt: "Jira API Token"
  • EnvVarNames: []string{"JIRA_TOKEN", "JIRA_API_TOKEN"}
  • EnvFileKeys: []string{"JIRA_TOKEN", "JIRA_API_TOKEN"}
  • ScopeIDField: "boardId"
  • ScopeFunc: scopeJiraHandler
• Implement scopeJiraHandler:
  • Use client.ListRemoteScopes("jira", connID, "", "") to list boards
  • Let user select boards interactively or via --board-ids flag
  • PUT selected boards as scopes
• Add JiraBoardScope struct (or build dynamically from remote-scope data)
• Set Available: true

Acceptance Criteria

• gh devlake configure connection add --plugin jira --endpoint https://mysite.atlassian.net creates a Jira connection
• Jira appears in interactive plugin picker
• Jira scopes list boards for selection
• Connection test works against Jira API
• go build ./..., go test ./..., go vet ./... pass

[ewega]

Agent Context for Implementation

This repo uses a declarative plugin registry pattern. Here's what you need to do:

1. Add ConnectionDef entry to cmd/connection_types.go

Add a new entry to connectionRegistry slice. Use the existing github entry as a template. Key fields for Jira:

• Plugin: "jira"
• DisplayName: "Jira"
• Available: true
• Endpoint: "" (user must provide, e.g. https://your-domain.atlassian.net/)
• SupportsTest: true
• AuthMethod: "AccessToken" (Jira Cloud uses API tokens)
• TokenPrompt: "Jira API token"
• EnvVarNames: []string{"JIRA_TOKEN", "JIRA_API_TOKEN"}
• EnvFileKeys: []string{"JIRA_TOKEN", "JIRA_API_TOKEN"}
• ScopeIDField: "boardId"
• ScopeFunc: scopeJiraHandler

2. Implement scopeJiraHandler in cmd/configure_scopes.go

Follow the pattern of scopeGitHubHandler. Use client.ListRemoteScopes("jira", connID, "", "") to list boards. Let user select interactively via prompt.SelectMulti. PUT selected boards as scopes.

3. Key conventions

• Use doGet[T], doPost[T] generic helpers from internal/devlake/client.go — never raw HTTP
• Error wrapping: fmt.Errorf("context: %w", err)
• Terminal output: \n before emoji-prefixed steps, 3-space indent for sub-items
• Imports: stdlib → external → internal, separated by blank lines
• Tests: add entries to cmd/connection_types_test.go verifying the new registry entry

4. Do NOT

• Add switch/case branches on plugin names outside connectionRegistry
• Modify existing plugin entries
• Change any files in internal/devlake/ unless adding new types needed for Jira scope responses