esigler / lita-jira

A JIRA plugin for Lita

Hi there 👋

lita-jira's Issues

Is there a way to search for jira username by email using user/picker in jira-lita.

My question is that the jira ticket gets created with the user id of the jira identified in lita_config.rb for jira, but is there a way to change this creator based on located in redis email?

todo shortcut crashes

pm2 version: 2.7.1
lita-jira version 0.9.0

When I try to add a jira task using 'todo' i get a crash:

0|lita | [2018-12-21 20:30:01 UTC] DEBUG: Dispatching message to Lita::Handlers::Jira#todo. 0|lita | [2018-12-21 20:30:03 UTC] ERROR: Lita::Handlers::Jira crashed. The exception was: 0|lita | Full backtrace: 0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/jira-ruby-1.6.0/lib/jira/request_client.rb:15:in request'
0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/jira-ruby-1.6.0/lib/jira/client.rb:238:in request' 0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/jira-ruby-1.6.0/lib/jira/client.rb:216:in get'
0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/jira-ruby-1.6.0/lib/jira/resource/issue.rb:95:in fetch' 0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-jira-0.9.0/lib/jirahelper/issue.rb:66:in create_issue'
0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-jira-0.9.0/lib/lita/handlers/jira.rb:106:in todo' 0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-4.7.1/lib/lita/callback.rb:31:in public_send'
0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-4.7.1/lib/lita/callback.rb:31:in call' 0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-4.7.1/lib/lita/handler/chat_router.rb:97:in dispatch_to_route'
0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-4.7.1/lib/lita/handler/chat_router.rb:82:in block in dispatch' 0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-4.7.1/lib/lita/handler/chat_router.rb:72:in map'
0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-4.7.1/lib/lita/handler/chat_router.rb:72:in dispatch' 0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-4.7.1/lib/lita/robot.rb:69:in block in receive'
0|lita | /opt/deployops/.rbenv/versions/2.2.6/lib/ruby/2.2.0/set.rb:283:in each_key' 0|lita | /opt/deployops/.rbenv/versions/2.2.6/lib/ruby/2.2.0/set.rb:283:in each'
0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-4.7.1/lib/lita/robot.rb:66:in map' 0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-4.7.1/lib/lita/robot.rb:66:in receive'
0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-slack-1.8.0/lib/lita/adapters/slack/message_handler.rb:122:in dispatch_message' 0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-slack-1.8.0/lib/lita/adapters/slack/message_handler.rb:159:in handle_message'
0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-slack-1.8.0/lib/lita/adapters/slack/message_handler.rb:18:in handle' 0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-slack-1.8.0/lib/lita/adapters/slack/rtm_connection.rb:100:in block in receive_message'
0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/lita-slack-1.8.0/lib/lita/adapters/slack/event_loop.rb:10:in block in defer' 0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/eventmachine-1.2.7/lib/eventmachine.rb:1077:in call'
0|lita | /opt/lita/releases/20181221171852Z/vendor/bundle/ruby/2.2.0/gems/eventmachine-1.2.7/lib/eventmachine.rb:1077:in block in spawn_threadpool'

When issue is unassigned, "jira details issueKey" causes a crash.

Test Case:

1. Create an issue as unassigned
2. Ask lita to fetch its summary via jira issueKey

Observe: works fine. Returns issue summary

1. Ask lita to fetch its details via jira details issueKey

Observe: Nothing returns in the chat, crash logs seen in lita's logs

[2015-02-26 18:01:31 UTC] ERROR: Lita::Handlers::Jira crashed. The exception was:
undefined method `displayName' for nil:NilClass
Full backtrace:
/usr/local/lib/ruby/gems/2.1.0/gems/lita-jira-0.5.0/lib/jirahelper/issue.rb:23:in `format_issue'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-jira-0.5.0/lib/lita/handlers/jira.rb:63:in `details'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita/callback.rb:31:in `public_send'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita/callback.rb:31:in `call'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita/handler/chat_router.rb:88:in `dispatch_to_route'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita/handler/chat_router.rb:73:in `block in dispatch'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita/handler/chat_router.rb:70:in `map'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita/handler/chat_router.rb:70:in `dispatch'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita/robot.rb:58:in `block in receive'
/usr/local/lib/ruby/2.1.0/set.rb:263:in `each_key'
/usr/local/lib/ruby/2.1.0/set.rb:263:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita/robot.rb:55:in `map'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita/robot.rb:55:in `receive'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-slack-1.1.0/lib/lita/adapters/slack/message_handler.rb:50:in `dispatch_message'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-slack-1.1.0/lib/lita/adapters/slack/message_handler.rb:85:in `handle_message'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-slack-1.1.0/lib/lita/adapters/slack/message_handler.rb:17:in `handle'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-slack-1.1.0/lib/lita/adapters/slack/rtm_connection.rb:97:in `receive_message'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-slack-1.1.0/lib/lita/adapters/slack/rtm_connection.rb:46:in `block (2 levels) in run'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/event_emitter.rb:31:in `call'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/event_emitter.rb:31:in `block in emit'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/event_emitter.rb:30:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/event_emitter.rb:30:in `emit'
/usr/local/lib/ruby/gems/2.1.0/gems/faye-websocket-0.9.2/lib/faye/websocket/api/event_target.rb:44:in `dispatch_event'
/usr/local/lib/ruby/gems/2.1.0/gems/faye-websocket-0.9.2/lib/faye/websocket/api.rb:95:in `receive_message'
/usr/local/lib/ruby/gems/2.1.0/gems/faye-websocket-0.9.2/lib/faye/websocket/api.rb:38:in `block in initialize'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/event_emitter.rb:31:in `call'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/event_emitter.rb:31:in `block in emit'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/event_emitter.rb:30:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/event_emitter.rb:30:in `emit'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/hybi.rb:397:in `emit_message'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/hybi.rb:380:in `emit_frame'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/hybi.rb:118:in `parse'
/usr/local/lib/ruby/gems/2.1.0/gems/websocket-driver-0.5.3/lib/websocket/driver/client.rb:57:in `parse'
/usr/local/lib/ruby/gems/2.1.0/gems/faye-websocket-0.9.2/lib/faye/websocket/api.rb:134:in `parse'
/usr/local/lib/ruby/gems/2.1.0/gems/faye-websocket-0.9.2/lib/faye/websocket/client.rb:77:in `receive_data'
/usr/local/lib/ruby/gems/2.1.0/gems/eventmachine-1.0.7/lib/eventmachine.rb:187:in `run_machine'
/usr/local/lib/ruby/gems/2.1.0/gems/eventmachine-1.0.7/lib/eventmachine.rb:187:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-slack-1.1.0/lib/lita/adapters/slack/rtm_connection.rb:37:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-slack-1.1.0/lib/lita/adapters/slack.rb:15:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita/robot.rb:69:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita.rb:79:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/lib/lita/cli.rb:77:in `start'
/usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
/usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
/usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
/usr/local/lib/ruby/gems/2.1.0/gems/lita-4.2.0/bin/lita:6:in `<top (required)>'
/usr/local/bin/lita:23:in `load'
/usr/local/bin/lita:23:in `<main>'

Search Jira Issue

How does it search for issues ? I have bunch of issues assigned to me and myissues returns null

Add cooldown to ambient detection

So that the same issue doesn't trigger multiple times within a window

Can't open a jira ticket using lita-jira

Reviewing ticket details is nice, but what would really be bomb is if we could create a ticket as well

Choosing field names to output when using ambient

It would be nice to have an option to choose the field names that are shown when using the ambient mode.

Error fetching JIRA issue

I have installed the gem "lita-jira" and am getting the following error when attempting to query a JIRA ticket.

!jira it-1651
Error fetching JIRA issue

If I run a JIRA api command via curl I am able to query the JIRA ticket using the same credentials.

##Jira
config.handlers.jira.username = 'jira.scripts'
config.handlers.jira.password = '******'
config.handlers.jira.site = 'http://jira.aofl.com:8080'
config.handlers.jira.context = ''
config.handlers.jira.format = 'one-line'

Can't search jira

Fetching ticket details are nice, but sometimes the name and/or number is hard to find! A search feature would be killer

Load error: cannot load such file -- jira

lita-jira-0.8.1/lib/lita-jira.rb:7:in require': cannot load such file -- jira (LoadError)`

as I see in documentation for jira-ruby it uses no more this Gemfile declaration:
gem 'jira-ruby', :require => 'jira'
it uses:
gem 'jira-ruby', :require => 'jira-ruby'
instead.

error when trying to add new ticket via todo

[2016-06-01 19:52:22 UTC] ERROR: JIRA HTTPError

Exception response: {"errorMessages":[],"errors":{"issuetype":"issue type is required"}}
[2016-06-01 19:52:38 UTC] ERROR: Lita::Handlers::Jira crashed. The exception was:
Method Not Allowed
Full backtrace:
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/jira-ruby-0.1.18/lib/jira/request_client.rb:16:in request' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/jira-ruby-0.1.18/lib/jira/client.rb:196:inrequest'
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/jira-ruby-0.1.18/lib/jira/client.rb:174:in get' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/jira-ruby-0.1.18/lib/jira/base.rb:339:infetch'
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-jira-0.8.1/lib/jirahelper/issue.rb:61:in create_issue' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-jira-0.8.1/lib/lita/handlers/jira.rb:104:intodo'
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-4.7.0/lib/lita/callback.rb:31:in public_send' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-4.7.0/lib/lita/callback.rb:31:incall'
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-4.7.0/lib/lita/handler/chat_router.rb:97:in dispatch_to_route' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-4.7.0/lib/lita/handler/chat_router.rb:82:inblock in dispatch'
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-4.7.0/lib/lita/handler/chat_router.rb:72:in map' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-4.7.0/lib/lita/handler/chat_router.rb:72:indispatch'
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-4.7.0/lib/lita/robot.rb:69:in block in receive' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/2.1.0/set.rb:263:ineach_key'
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/2.1.0/set.rb:263:in each' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-4.7.0/lib/lita/robot.rb:66:inmap'
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-4.7.0/lib/lita/robot.rb:66:in receive' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-slack-1.7.2/lib/lita/adapters/slack/message_handler.rb:119:indispatch_message'
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-slack-1.7.2/lib/lita/adapters/slack/message_handler.rb:159:in handle_message' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-slack-1.7.2/lib/lita/adapters/slack/message_handler.rb:18:inhandle'
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-slack-1.7.2/lib/lita/adapters/slack/rtm_connection.rb:100:in block in receive_message' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/lita-slack-1.7.2/lib/lita/adapters/slack/event_loop.rb:10:inblock in defer'
/usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/eventmachine-1.2.0.1/lib/eventmachine.rb:1076:in call' /usr/local/var/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/eventmachine-1.2.0.1/lib/eventmachine.rb:1076:inblock in spawn_threadpool'

Jira http error end of file reached

When I try and use lita-jira to return a ticket reference, I get ERROR: JIRA HTTPError end of file reached

config file settings:

config.handlers.jira.username = "*****"
config.handlers.jira.password = "******"
config.handlers.jira.url = "https://<jira url>"
config.handlers.jira.use_ssl = false #self signed cert

Triggers on the middle of strings

Currently with ambient set to true the bot is triggering on links to artifacts that happen to match a jira project. We have a jira project with the key 'WEB' and links like http://artifactory-server/artifact-web-1.0.0.war will trigger the bot to report about WEB-1, which is a valid ticket in our system. Ideally, the regex should be using word boundaries to not trigger in the middle of a longer name.