Skip to content

meanbee/slack-jira-bot

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
src
 
 
 
 
 
 
 
 
 
 
 
 

(Deprecated) Slack Jira Issue Expansion

Notice: This project is no longer being maintained and the APIs that is uses are deprecated.

Build Status

Update 2017-08-24: If you're looking to get setup quickly then you should check out https://slack.atlassian.io before using this image. If that's not for you - come back!

A killer feature of the integration between Hipchat and Jira is the issue expansion. Whenever a Jira issue is mention in the chat, the Jira integration would pop up some high level information about the issue and a link.

With the Jira integration in Slack being a bit light, we decided to implement a simple bot using the Slack RTM API:

Installation

Docker Image

docker run -it --restart=always -d \
    -e JIRA_BASEURL=https://yourjirainstall.atlassian.net \
    -e JIRA_USERNAME='yourjirausername' \
    -e JIRA_PASSWORD='yourjirapassword' \
    -e SLACK_API_KEY='yourslackapikey' \
    meanbee/slack-jira-bot:latest

Configuration

The configuration is run of environment variables:

  • SLACK_API_KEY
  • JIRA_BASEURL, e.g. https://yourcompany.atlassian.net
  • JIRA_USERNAME
  • JIRA_PASSWORD

About

Provide URL expansion when Jira issues are mentioned in a Slack chat

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published