It looks like commander's description of the command and the JIRA argument --description are colliding. For example, if you were to console.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#L294 options[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.
It looks like
commander's description of the command and the JIRA argument --description are colliding. For example, if you were toconsole.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]foreachFieldKey = description, this comes out astruebecause of the[Function]and so the CLI does not ask for a description and tries to create a JIRA ticket without adescriptionfield which causes a 400 because this field is required.I tried making this required in every possible way without any success.