When the jira plugin is loaded for the first time, there is nothing stored in the brain. This causes @cache to get set to null which results in errors being thrown during @cache.forEach Only set the cache to data from the brain if that data exists.
- Improved documentation since issues could mean GitHub or other trackers - <name> needs to be specified to use a filter - Filter names are no longer case sensitive - Error message when a filter isn't found
This commit improves help messages for a lot of the scripts. In particular: * Include hubot at the beginning of `respond`s * Keep help messages to one line * separate example and documentation by a single space, a hyphen, and another space (as opposed to verticaly aligning the hyphen)
Had issues with hubot entering an infinite loop when responding to an issue search
… HUBOT_JIRA_ISSUEDELAY to control number of seconds before an issue can be reposted. Cleanup of LISTMAX variables.
… results returned. Link included to issue search page in web UI.
…ername mention instead of user id in reply.
…ROJ-324 or PROJ-355" would have previously only posted the link to 324, now it will show both)
… be sure to add HUBOT_JIRA_USE_V2=true environment variable)