You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Fetch permissions in heartbeat
* Obtain projects permissions in parallel calls
* Updating call to jira_client as get_permissions
* Updating tests
* Refactor: fetch and validation are now separate functions; JIRA_REQUIRED_PERMISSIONS changed to an env var.
* Use custom Jira client to avoid waiting for release
* Fix linting and mocking
* Manage list of required permissions at action module level (mozilla#177)
* Manage list of required permissions at action module level
* Fix list of missing permissions
* Use atlassian-python-api @ master instead of release + inherited class
Co-authored-by: Bryan Sieber <[email protected]>
Copy file name to clipboardExpand all lines: jbi/actions/README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,8 @@ Let's create a `new_action`!
13
13
```python
14
14
from jbi import ActionResult, Operation
15
15
16
+
JIRA_REQUIRED_PERMISSIONS= {"CREATE_ISSUES"}
17
+
16
18
definit(jira_project_key, optional_param=42):
17
19
18
20
defexecute(payload) -> ActionResult:
@@ -28,6 +30,7 @@ Let's create a `new_action`!
28
30
1. The returned `ActionResult` features a boolean to indicate whether something was performed or not, along with a `Dict` (used as a response to the WebHook endpoint).
29
31
30
32
1. Use the `payload` to perform the desired processing!
33
+
1. List the required Jira permissions to be set on projects that will use this action in the `JIRA_REQUIRED_PERMISSIONS` constant. The list of built-in permissions is [available on Atlanssian API docs](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-permission-schemes/#built-in-permissions).
31
34
1. Use the available service calls from `jbi/services.py` (or make new ones)
32
35
1. Update the `README.md` to document your action
33
36
1. Now the action `jbi.actions.my_team_actions` can be used in the YAML configuration, under the `module` key.
0 commit comments