Skip to content

Commit 0dd338d

Browse files
author
Bryan Sieber
committed
Updating README: adding badges, updating section information.
1 parent c6c24a0 commit 0dd338d

File tree

1 file changed

+53
-7
lines changed

1 file changed

+53
-7
lines changed

README.md

Lines changed: 53 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,58 @@
1+
![build badge](https://github.com/mozilla/jira-bugzilla-integration/actions/workflows/build-image.yaml/badge.svg)
2+
![test badge](https://github.com/mozilla/jira-bugzilla-integration/actions/workflows/test-build.yaml/badge.svg)
3+
14
# Jira Bugzilla Integration (JBI)
2-
System to sync bugs and issues
5+
System to sync Bugzilla bugs to Jira issues.
6+
7+
### Caveats
8+
- The system accepts webhook events from Bugzilla
9+
- The events are transformed into Jira issues
10+
- The system POSTs an update to the see_also field of Bugzilla bugs
11+
- Bugs' whiteboard tags are used to determine if they should be synchronized or ignored
312

413
## Self-Service
514

6-
If you're interested in using the default action;
7-
the process is simple to enabling a new downstream
8-
project. [...read more here.](src/jbi/whiteboard_tags/README.md)
15+
### Action Configuration
16+
The action configuration uses a YAML file per environment, this file stores all the configuration information for jbi data flows. The process to enable a new data flow will be explained below.
17+
18+
19+
Below is an full example of an action configuration:
20+
```yaml
21+
action: src.jbi.whiteboard_actions.default
22+
contact: [[email protected]]
23+
description: example configuration
24+
enabled: true
25+
parameters:
26+
jira_project_key: EXMPL
27+
whiteboard_tag: example
28+
```
29+
30+
A bit more about the different fields...
31+
- `action` (optional)
32+
- string
33+
- default: [src.jbi.whiteboard_actions.default](src/jbi/whiteboard_actions/default.py)
34+
- If using a custom action, place the PYTHONPATH to the custom action python module
35+
- `contact`
36+
- list of strings
37+
- If an issue arises with the workflow, communication will be established with this `contact`
38+
- Please enter the contact information for one or more stakeholders
39+
- `description`
40+
- string
41+
- Please enter a description; for example, team name or project use-case.
42+
- `enabled` (optional)
43+
- bool [true, false]
44+
- default: false
45+
- If false, matching events will not be synchronized
46+
- `parameters` (optional)
47+
- dict
48+
- default: {}
49+
- The parameters will be validated to ensure the selected action has all expected parameters
50+
- The [default action](src/jbi/whiteboard_actions/default.py) expects both the `whiteboard_tag` and `jira_project_key` fields
51+
52+
53+
[View 'dev' configurations here.](config/config.dev.yaml)
54+
[View 'prod' configurations here.](config/config.prod.yaml)
55+
956

10-
If you're looking for a unique capability for your
11-
team's data flow; you can add your own python methods
12-
and functionality. [...read more here.](src/jbi/whiteboard_actions/README.md)
57+
### Custom Actions
58+
If you're looking for a unique capability for your team's data flow, you can add your own python methods and functionality[...read more here.](src/jbi/whiteboard_actions/README.md)

0 commit comments

Comments
 (0)