Create a standard API between DejaCode Requests and Atlassian JIRA

[DennisClark]

We need a way for a DejaCode Superuser, who is also an Atlassian JIRA administrator, to use the DejaCode UI to configure integration between DejaCode Requests and JIRA Issues (requests, tickets, whatever). Design needed of course. Potential approaches include the following:

1. Submit a JIRA issue on DejaCode Request addition:

We could use the DejaCode Webhook system (already supported for Slack), to add a mapping for JIRA.

• https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis#JIRARESTAPIs-ASimpleExample:CreatinganIssueinJIRA
• https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-create-issue

2. Create a DejaCode Request on JIRA issue addition:

A JIRA Webhook needs to be configured, providing a DejaCode URL that would receive the data from JIRA and map it into a DejaCode issue creation. See

• https://developer.atlassian.com/jiradev/jira-apis/webhooks

[lucasgonze]

A use case may help.

A compliance specialist is checking licensing problems flagged by the tool. They find an item using the AGPL. Company policy is to review usage context first. They create a Jira ticket with contextual information about the application, component, and license. They assign the ticket to an attorney, who evaluates the application. The attorney concludes that the component must be removed. The Jira ticket is assigned to an engineer, who follows links to the component source repository to find a replacement component and then code the change, then marks the work as done. The ticket is reassigned to the compliance specialist, who removes the AGPL issue as a blocker on acceptance of the application.

[DennisClark]

@lucasgonze thanks very much for the use case, which will be quite helpful when we get into the design details.