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
It looks like commander's description of the command and the JIRA argument --description are colliding. For example, if you were to console.logoptions['description'] here https://github.com/danshumaker/jira-cli/blob/master/bin/jira.js#L284, then you'll see the value is a [Function].
The end result is if you were to run jira new KEY, at this line https://github.com/danshumaker/jira-cli/blob/master/lib/jira/new.js#L294options[eachFieldKey] for eachFieldKey = description, this comes out as true because of the [Function] and so the CLI does not ask for a description and tries to create a JIRA ticket without a description field which causes a 400 because this field is required.
I tried making this required in every possible way without any success.
The text was updated successfully, but these errors were encountered:
It looks like
commander
's description of the command and the JIRA argument --description are colliding. For example, if you were toconsole.log
options['description']
here https://github.com/danshumaker/jira-cli/blob/master/bin/jira.js#L284, then you'll see the value is a[Function]
.The end result is if you were to run
jira new KEY
, at this line https://github.com/danshumaker/jira-cli/blob/master/lib/jira/new.js#L294options[eachFieldKey]
foreachFieldKey = description
, this comes out astrue
because of the[Function]
and so the CLI does not ask for a description and tries to create a JIRA ticket without adescription
field which causes a 400 because this field is required.I tried making this required in every possible way without any success.
The text was updated successfully, but these errors were encountered: