Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add GitHub / Jira integration #962

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 42 additions & 0 deletions .github/.jira_sync_config.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# This is a templated file and must be kept up-to-date with the original
# from upstream at https://github.com/canonical/se-tooling-ci-common.
#
# Add this file to .github/.jira_sync_config.yaml
settings:
# Jira project key to create the issue in
jira_project_key: "SET"

# Dictionary mapping GitHub issue status to Jira issue status
status_mapping:
opened: Wishlist
closed: Done

# (Optional) Jira project components that should be attached to the created
# issue Component names are case-sensitive
components:
- hotsos

# (Optional) GitHub labels. Only issues with one of those labels will be
# synchronized. If not specified, all issues will be synchronized
# labels:
# - jira

# (Optional) (Default: false) Add a new comment in GitHub with a link to Jira
# created issue
add_gh_comment: true

# (Optional) (Default: true) Synchronize issue description from GitHub to Jira
sync_description: true

# (Optional) (Default: true) Synchronize comments from GitHub to Jira
sync_comments: true

# (Optional) (Default: None) Parent Epic key to link the issue to
epic_key: "SET-926"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is this epic? does it need to be changed to a different one before we use this with hotsos?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just a "catch-all" epic used for anything coming from GitHub using this integration. We can of course change that to some other Epic.


# (Optional) Dictionary mapping GitHub issue labels to Jira issue types. If
# label on the issue is not in specified list, this issue will be created as a
# Bug
label_mapping:
enhancement: Story
bug: Story
Loading