https://github.com/release-engineering/sync2jira

Service to sync upstream Tickets/PR's with downstream JIRA tickets!
https://github.com/release-engineering/sync2jira

Last synced: about 1 year ago
JSON representation

Service to sync upstream Tickets/PR's with downstream JIRA tickets!

• Host: GitHub
• URL: https://github.com/release-engineering/sync2jira
• Owner: release-engineering
• License: lgpl-2.1
• Created: 2019-11-25T14:28:29.000Z (over 6 years ago)
• Default Branch: main
• Last Pushed: 2025-04-03T20:44:10.000Z (about 1 year ago)
• Last Synced: 2025-04-03T21:31:33.602Z (about 1 year ago)
• Language: Python
• Size: 791 KB
• Stars: 14
• Watchers: 4
• Forks: 25
• Open Issues: 21
• Metadata Files:
  • Readme: README.md
  • License: LICENSE
  • Codeowners: CODEOWNERS

Awesome Lists containing this project

README

          
# Sync2Jira

[![Documentation Status](https://readthedocs.org/projects/sync2jira/badge/?version=master)](https://sync2jira.readthedocs.io/en/master/?badge=master)

[![Docker Repository on Quay](https://quay.io/repository/redhat-aqe/sync2jira/status "Docker Repository on Quay")](https://quay.io/repository/redhat-aqe/sync2jira)

[![Build Status](https://travis-ci.org/release-engineering/Sync2Jira.svg?branch=master)](https://travis-ci.org/release-engineering/Sync2Jira)

[![Coverage Status](https://coveralls.io/repos/github/release-engineering/Sync2Jira/badge.svg?branch=master)](https://coveralls.io/github/release-engineering/Sync2Jira?branch=master)

![Python 3.7](https://img.shields.io/badge/python-3.7-blue.svg)

## What is Sync2Jira?

This is a process that listens to activity on upstream repos on

GitHub via fedmsg, and syncs new issues there to a Jira instance elsewhere.

## Documentation

Documentation is hosted on readthedocs.io and can be found [here](https://sync2jira.readthedocs.io/en/latest/)

## Configuration

We have set up a quick-start [here](https://sync2jira.readthedocs.io/en/master/quickstart.html)

Configuration is in folder `fedmsg.d`.

You can maintain a mapping there that allows you to match one upstream repo

(say, 'pungi') to a downstream project/component pair in Jira (say,

'COMPOSE', and 'Pungi').

On startup:

- in `fedmsg.d/sync2jira.py`, if the `testing` option is set to `True`, then the script will perform a "dry run" and not actually add any new issues to Jira.

- if the `INITIALIZE` environment variable is set to `1`, the script will sync all issues to Jira. Use caution as this may be very expensive and difficult to undo.

Please look at our documentation [here](https://sync2jira.readthedocs.io/en/master/config-file.html) for a full list of what can be synced and how to set it up.