https://github.com/cybervoid/gajira-get-issue
Finds a Jira Issue from string
https://github.com/cybervoid/gajira-get-issue
Last synced: 4 months ago
JSON representation
Finds a Jira Issue from string
- Host: GitHub
- URL: https://github.com/cybervoid/gajira-get-issue
- Owner: cybervoid
- License: apache-2.0
- Created: 2020-03-25T14:34:14.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2022-08-18T19:24:32.000Z (almost 4 years ago)
- Last Synced: 2026-02-11T18:48:48.584Z (4 months ago)
- Language: JavaScript
- Size: 151 KB
- Stars: 1
- Watchers: 1
- Forks: 4
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# gajira-get-issue
Finds a Jira Issue from string
## Usage
To easily find Jira issue from commits or branch, I recommend [Jira Find issue key](https://github.com/marketplace/actions/jira-find-issue-key), the official Jira's release action. What's different with this action,
if you still need to find an issue when a PR is opened or even when the PR is merged, this action will receive any string and try to find it there and if it's not found, then it will go to the github object and try to find
it from messages created by github.
> ##### Note: this action is compatible with the official Jira actions [Jira Login Action](https://github.com/marketplace/actions/jira-login)
To find an issue key inside commit messages:
```yaml
- name: Find in commit messages
uses: cybervoid/gajira-get-issue@v1.0
with:
input-text: ${{ github.ref }}
```
----
## Action Spec:
### Environment variables
- None
### Inputs
- `input-text` - Provide any string to extract issue from
### Outputs
- `issue` - Key of the found issue
### Reads fields from config file at $HOME/jira/config.yml
- None
### Writes fields to config file at $HOME/jira/config.yml
- `issue` - a key of a found issue
### Writes fields to CLI config file at $HOME/.jira.d/config.yml
- `issue` - a key of a found issue