LogoRobo.js
Packages@robojs/roadmap

JiraProviderConfig

Interface: JiraProviderConfig

Configuration shape for the JiraProvider.

Remarks

Values can be provided directly on the config object, through the options bag, or via environment variables. Explicit config values take precedence, followed by option values, with environment variables acting as the final fallback. Missing required credentials will be surfaced during JiraProvider.validateConfig.

Extends

Properties

PropertyModifierTypeDescriptionOverridesInherited from
apiToken?readonlystringJira API token associated with the Atlassian account.--
defaultIssueType?readonlystringDefault issue type name for created issues (e.g., 'Epic', 'Task'). Defaults to 'Task' if not specified.--
discordUserIdFieldId?readonlystringJira custom field ID containing Discord User ID (e.g., 'customfield_10001'). When set, this field takes priority over Jira assignee mapping. The field should contain a Discord User ID (17-19 digit numeric string).--
email?readonlystringAtlassian account email used for API authentication.--
jql?readonlystringOptional JQL query to scope the issues returned by the provider.--
maxResults?readonlynumberMaximum number of issues to fetch per page when paging Jira search results.--
optionsreadonlyRecord<string, unknown> & { apiToken: string; columnConfig: ColumnConfig; defaultIssueType: string; discordUserIdFieldId: string; email: string; jql: string; maxResults: number; projectKey: string; url: string; }Provider options bag allowing runtime overrides via plugin configuration.ProviderConfig.options-
projectKey?readonlystringJira project key for creating issues (e.g., 'PROJ').--
typereadonlystringProvider type identifier (e.g., jira, github).-ProviderConfig.type
url?readonlystringFully qualified Jira Cloud base URL, e.g., https://example.atlassian.net.--

On this page