hungngit2/Jira Ticket Transition and Environment Info
Fetches Jira ticket release information and updates the environment table in the ticket.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| JIRA_BASE_URL | Jira base URL, e.g. https://your-domain.atlassian.net | yes | — |
| JIRA_USER_EMAIL | Jira user email, e.g. yourname@your-domain | yes | — |
| JIRA_API_TOKEN | Jira API token | yes | — |
| JIRA_ISSUE_KEY | Jira issue key, e.g. ABC-1234 | yes | — |
| JIRA_ENV_COLUMNS | Comma separated columns for environment table, e.g. Environment,Branch,Path to Build,Path to Upsert | no | — |
| JIRA_ISSUE_KEY_PATTERN | Default: ([A-Z0-9]+)[\\s-]?(\\d+) | no | — |
| JIRA_ISSUE_TYPE_TRANSITION | Default: "Story:Code Review;Bug:Code Revieww" | no | — |
| JIRA_COMMENT_BODY | Comment body to add to the Jira issue | no | — |
| LINEAR_API_TOKEN | Linear API token. When set, Linear is tried first before falling back to Jira. | no | — |
| LINEAR_ISSUE_KEY | Linear issue identifier, e.g. ENG-123. Defaults to JIRA_ISSUE_KEY if not set. | no | — |
| LINEAR_COMMENT_BODY | Comment body to add to the Linear issue (falls back to JIRA_COMMENT_BODY if not set) | no | — |
| ISSUE_TRACKER | Explicit tracker selection: "linear" or "jira". Omit to auto-detect (Linear if LINEAR_API_TOKEN is set, else Jira). When Linear is selected but the issue is not found, the action always falls back to Jira. | no | — |
| ACTIONS_MODE | Mode of action to perform: "NewComment", "Transition", or "IssueInfo" | no | — |
Outputs
no outputs