Lets you search for JIRA tickets, open them, transition them thru different states, comment on them, rank them up or down, start or stop watching them or change who is assigned to a ticket. Also, notifications for assignments, mentions and watched tickets.
Aside from the fact that there's no information on what is parsable from environment variables as opposed to only being picked up from ~/src/config, the HUBOT_JIRA_GITHUB_DISABLED does not seem to be acknowledged at all. I've set it in:
1) env-wide for the user running hunot
2) process-wide with the startup of hubot
3) in the ./config file expected to be under ~/src, which is evidently the only place most other vars are picked up from
Still, on hubot startup I get errors on pull-req coffee for github tokens missing.
A simple explanation on what the default set of env vars required for starting up with jira only, withouth gitihub and anything else like statd would be highly appreciated.
The second thing is that statd is not optional at all, utils parsing fails without its relevant options being present in ./config, so it has to be removed with extreme prejudice from 2+ files to get the thing to start.
Additionally, there's undocumented options in the README.md versus what's under comments of config.
Aside from the fact that there's no information on what is parsable from environment variables as opposed to only being picked up from ~/src/config, the HUBOT_JIRA_GITHUB_DISABLED does not seem to be acknowledged at all. I've set it in:
1) env-wide for the user running hunot 2) process-wide with the startup of hubot 3) in the ./config file expected to be under ~/src, which is evidently the only place most other vars are picked up from
Still, on hubot startup I get errors on pull-req coffee for github tokens missing.
A simple explanation on what the default set of env vars required for starting up with jira only, withouth gitihub and anything else like statd would be highly appreciated.
The second thing is that statd is not optional at all, utils parsing fails without its relevant options being present in ./config, so it has to be removed with extreme prejudice from 2+ files to get the thing to start.
Additionally, there's undocumented options in the README.md versus what's under comments of config.