Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/iolave/bun-jira-tickets-from-gh
CLI tool to sync your GitHub project to Jira Project
https://github.com/iolave/bun-jira-tickets-from-gh
atlassian automation bun cli github-projects jira
Last synced: 14 days ago
JSON representation
CLI tool to sync your GitHub project to Jira Project
- Host: GitHub
- URL: https://github.com/iolave/bun-jira-tickets-from-gh
- Owner: iolave
- License: apache-2.0
- Created: 2024-08-26T14:41:20.000Z (26 days ago)
- Default Branch: master
- Last Pushed: 2024-09-04T21:48:12.000Z (17 days ago)
- Last Synced: 2024-09-06T05:08:06.735Z (15 days ago)
- Topics: atlassian, automation, bun, cli, github-projects, jira
- Language: TypeScript
- Homepage: https://www.npmjs.com/package/jira-tickets-from-gh
- Size: 64.5 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# Sync Jira and GitHub projects
I was forced by my job to use Jira to keep track of tasks, but I kept forgetting to update status within Jira. Most of time im in GitHub and it's just easier to have issues and close them via PR's.
...so i built this tool for myself and hopefully, it will help you too.
> [!WARNING]
> All versions released prior to `v1.0.0` are to be considered [breaking changes](https://semver.org/#how-do-i-know-when-to-release-100) (I'll try my best to not push breaking changes btw).
To install dependencies:
## Pre-requisites for running the CLI
### A GitHub project with required fields
Make sure you have a GitHub project with the following fields:
- `Title`: Title for the task.
- `Jira issue type`: choice field with available jira issue types.
- `Jira URL`: text field to store jira url.
- `Status`: `Todo`, `In Progress`, `Done` choice field.
- `Estimate`: Number field.
- `Repository`: Default field for repository info.
### Get the id of your github project
#### Organization projects
The cli is shipped with a utility that's going to help us search our GitHub project id.
```bash
jira-tickets-from-gh --gh-token=GH_TOKEN github-projects listOrganization --org=YOU_ORG
```
#### User projects
_NOT YET AVAIALBLE_
### Get a Jira cloud token
- Get a jira api token from your jira cloud account.
- Form a base64 encoded string (basic auth) out of your jira cloud account and the api token: `base64(EMAIL:API_TOKEN)`.
### Environment variables
- `GITHUB_TOKEN`: Your GitHub token. If the project you're trying to sync is in an organization, make sure the token have access to it.
- `JIRA_TOKEN`: Basic authorization token, to form it `base64([JIRA_CLOUD_ACCOUNT]:[JIRA_API_KEY])`
## Using the CLI to sync projects
Install the CLI
```bash
bun install -g jira-tickets-from-gh
```
Use `jira-tickets-from-gh sync [Options]` command to sync a GitHub project with a Jira cloud project.
| Option | Required | Description |
|---------------------------------------------|----------|-------------|
|`--transitions-to-wip ` | `false` | list of jira issue transitions in order to have a wip task |
|`--transitions-to-done ` | `false` | list of jira issue transitions in order to have a done task |
|`--gh-assignees-map ` | `false` | map of GitHub users to Jira ones (email) |
|`--sleep-time ` | `false` | sleep time between executions. If not specified the program will run once |
|`--gh-project-id ` | `true` | Github project ID |
|`--jira-project-key ` | `true` | Jira project KEY |
|`--jira-subdomain ` | `true` | Jira subdomain |
|`--help` | `false` | display help for command |
### Example
*Using environment variables*
```bash
export GITHUB_TOKEN=token
export JIRA_TOKEN=token
jira-tickets-from-gh sync \
--gh-project-id=PROJECT_ID \
--jira-project-key=PROJECT_KEY \
--jira-subdomain=MYSUBDOMAIN \
--gh-assignees-map=iolave:[email protected]
```
*Passing tokens via the cli*
```bash
export GITHUB_TOKEN=token
export JIRA_TOKEN=token
jira-tickets-from-gh --gh-token=TOKEN --jira-token=TOKEN sync \
--gh-project-id=PROJECT_ID \
--jira-project-key=PROJECT_KEY \
--jira-subdomain=MYSUBDOMAIN \
--gh-assignees-map=iolave:[email protected]
```
*Execution example*
```
[2024-08-01 10:45:46][INFO] syncCmd.action creating jira issue {"title":"TEST: bun-jira-tickets-from-gh"}
[2024-08-01 10:45:47][INFO] syncCmd.action created issue {"url":"https://mfhnet.atlassian.net/browse/TEST3-112"}
```
## Running using Docker
### Environment variables
| Env | Maps to option |
|-----------------------|-------------------------|
| GITHUB_TOKEN | `--gh-token` |
| GH_PROJECT_ID | `--gh-project-id` |
| GH_USERS_MAP | `--gh-assignees-map` |
| JIRA_TOKEN | `--jira-token` |
| JIRA_SUBDOMAIN | `--jira-subdomain` |
| JIRA_PROJECT_KEY | `--jira-project-key` |
| JIRA_WIP_TRANSITIONS | `--transitions-to-wip` |
| JIRA_DONE_TRANSITIONS | `--transitions-to-done` |
| SLEEP_TIME | `--sleep-time` |
### Build
```bash
docker compose build
```
### Run
```bash
docker compose --env-file=path/to/env up -d
```