You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calling jira_client.Attachment.build(issue: issue) where issue is a JIRA::Resource::Issue I come across the following stack trace.
6: from /Users/$USER/.rvm/gems/ruby-2.6.1/gems/jira-ruby-1.6.0/lib/jira/base_factory.rb:43:in `build'
5: from /Users/$USER/.rvm/gems/ruby-2.6.1/gems/jira-ruby-1.6.0/lib/jira/base.rb:117:in `build'
4: from /Users/$USER/.rvm/gems/ruby-2.6.1/gems/jira-ruby-1.6.0/lib/jira/base.rb:117:in `new'
3: from /Users/$USER/.rvm/gems/ruby-2.6.1/gems/jira-ruby-1.6.0/lib/jira/base.rb:80:in `initialize'
2: from /Users/$USER/.rvm/gems/ruby-2.6.1/gems/jira-ruby-1.6.0/lib/jira/base.rb:80:in `each'
1: from /Users/$USER/.rvm/gems/ruby-2.6.1/gems/jira-ruby-1.6.0/lib/jira/base.rb:90:in `block in initialize'
ArgumentError (Required option :issue missing)
Walking through the code it looks like in base.rb:117 it callsnew(client, attrs: attrs) which calls into it's initializer. In the init expects issue to be in the top level of the hash however it's nested 1 down because it's passed through the attr.
The text was updated successfully, but these errors were encountered:
When calling
jira_client.Attachment.build(issue: issue)
where issue is a JIRA::Resource::Issue I come across the following stack trace.Walking through the code it looks like in
base.rb:117
it callsnew(client, attrs: attrs)
which calls into it's initializer. In the init expectsissue
to be in the top level of the hash however it's nested 1 down because it's passed through theattr
.The text was updated successfully, but these errors were encountered: