v1.4.1

1.4.1 (2018-10-12)

Bug Fixes

• only add one example JIRA key to warning (#47) (56dee38)

v1.4.0

1.4.0 (2018-10-04)

Features

• options: add location to options (#44) (96e6261)

v1.3.0

<a name"1.3.0">

1.3.0 (2017-11-30)

Features

• $options: Adds message format function to options (#33) (ecfead90)

v1.2.0

1.2.0 (2017-09-20)

Features

• support multiple JIRA projects (#26) (f0a084ff, closes #24)

If you work with multiple JIRA project boards, you can supply multiple project keys:

jiraIssue({
  key: ['ABC', 'DEF'],
  url: 'https://myjira.atlassian.net/browse',
})

This plugin will recognize issues starting with those keys (e.g. ABC-123 and DEF-234).

v1.1.0

<a name"1.1.0">

1.1.0 (2017-06-02)

Features

• support multiple JIRA issues in PR title (86c01d0e, closes #8)

v1.0.2

<a name"1.0.2">

1.0.2 (2017-05-17)

Bug Fixes

• jiraIssue: properly resolve URL (af099b9f)

v1.0.1

1.0.1 (2017-05-14)

Bug Fixes

• node: support Node 4 (d89d6510)

v1.0.0

1.0.0 (2017-05-12)

Features

• jiraIssue: add initial implementation (#1) (8638e2f1)

jiraIssue() is a Danger plugin that adds a JIRA issue link to the Danger pull request comment.
If a pull request title does not contain the supplied JIRA issue identifier (e.g. ABC-123),
then Danger will comment with a warning on the pull request asking the developer
to include the JIRA issue identifier in the pull request title.

Example usage:

// dangerfile.js
import jiraIssue from 'danger-plugin-jira-issue'

jiraIssue({
  key: 'JIRA',
  url: 'https://myjira.atlassian.net/browse',
  emoji: ':paperclip:',
})

Breaking Changes

• this commit introduces functionality ready for a 1.0.0 release.
  (8638e2f1)