2017-06-20 03:33:39 +02:00
|
|
|
*If you are running JIRA version 5.2 or greater, or using the hosted
|
2017-06-05 17:27:59 +02:00
|
|
|
JIRA provided by Atlassian, we recommend using the
|
2017-07-25 03:15:21 +02:00
|
|
|
[web-hook method](./jira) above instead. This plugin supports older
|
2017-06-20 03:33:39 +02:00
|
|
|
versions of JIRA.*
|
2017-06-05 17:27:59 +02:00
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
{!create-stream.md!}
|
2017-06-05 17:27:59 +02:00
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
### Plugin mechanism
|
2017-06-05 17:27:59 +02:00
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
{!download-python-bindings.md!}
|
2017-06-05 17:27:59 +02:00
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
#### Plugin Installation
|
2017-06-05 17:27:59 +02:00
|
|
|
|
|
|
|
The JIRA integration plugin requires two JIRA plugins. Please install
|
2017-06-20 03:33:39 +02:00
|
|
|
the following plugins using the **Universal Plugin Manager** in your
|
|
|
|
JIRA installation:
|
2017-06-05 17:27:59 +02:00
|
|
|
|
|
|
|
* [Script Runner Plugin][script-runner]
|
|
|
|
* [SSL Plugin][ssl-plugin]
|
|
|
|
|
|
|
|
[script-runner]: https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner
|
|
|
|
[ssl-plugin]: https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.jirasslplugin
|
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
#### SSL Setup
|
2017-06-05 17:27:59 +02:00
|
|
|
|
|
|
|
As Zulip is using a StartCOM SSL certificate that is not recognized by
|
|
|
|
default in the Java installation shipped with JIRA, you will need to
|
|
|
|
tell JIRA about the certificate.
|
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
1. Navigate to **Administration > System > Configure SSL** and in the
|
|
|
|
**Import SSL Certificates** field, enter `{{ external_api_uri_subdomain }}`.
|
2017-06-05 17:27:59 +02:00
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
2. After clicking **Save Certificates**, follow the on-screen
|
|
|
|
instructions and restart JIRA for it to recognize the proper
|
|
|
|
certificates.
|
2017-06-05 17:27:59 +02:00
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
#### Zulip Integration
|
2017-06-05 17:27:59 +02:00
|
|
|
|
|
|
|
1. Copy the folder `integrations/jira/org/` (from the tarball you
|
2017-06-20 03:33:39 +02:00
|
|
|
downloaded above) to your JIRA `classes` folder. For self-contained
|
|
|
|
JIRA installations, this will be `atlassian-jira/WEB-INF/classes/`,
|
|
|
|
but this may be different in your deployment.
|
2017-06-05 17:27:59 +02:00
|
|
|
|
|
|
|
2. Edit the constants at the top of
|
2017-06-20 03:33:39 +02:00
|
|
|
`org/zulip/jira/ZulipListener.groovy` and fill them with the
|
|
|
|
appropriate values:
|
2017-06-05 17:27:59 +02:00
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
``` Python
|
2017-06-05 17:27:59 +02:00
|
|
|
String zulipEmail = "jira-notifications-bot@example.com"
|
|
|
|
String zulipAPIKey = "0123456789abcdef0123456789abcdef"
|
2017-06-20 03:33:39 +02:00
|
|
|
String zulipStream = "{{ recommended_stream_name }}"
|
2017-06-05 17:27:59 +02:00
|
|
|
String issueBaseUrl = "https://jira.COMPANY.com/browse/"
|
|
|
|
```
|
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
3. On the **Administrators** page, navigate to
|
|
|
|
**Plugins > Other > Script Listeners**.
|
2017-06-05 17:27:59 +02:00
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
4. In the **Add Listener** section, click on the **Custom Listener**
|
|
|
|
option. Select the events you wish the Zulip integration to fire for,
|
|
|
|
and the projects you wish Zulip to be notified for.
|
2017-06-05 17:27:59 +02:00
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
5. In the **Name of groovy class** field, enter
|
|
|
|
`org.zulip.jira.ZulipListener`.
|
2017-06-05 17:27:59 +02:00
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
6. Click **Add Listener**, and JIRA will now notify your Zulip of
|
|
|
|
changes to your issues! Updates from JIRA will be sent to the stream
|
|
|
|
you've configured.
|
2017-06-05 17:27:59 +02:00
|
|
|
|
2017-06-20 03:33:39 +02:00
|
|
|
{!congrats.md!}
|
2017-06-05 17:27:59 +02:00
|
|
|
|
|
|
|
![](/static/images/integrations/jira/001.png)
|