Unable to create issue due to additional required fields about jira-cli HOT 5 OPEN

Here is an example of the types for the project I found this issue on originally.

["issuetype","array","string","project","option","timetracking","any","date","user","priority","issuelink"]

It looks like just strings should be okay, as my guess is all of these would have to be typed as strings for the JSON request anyways.

from jira-cli.

This could be fairly easy to implement as you said, however, I'm thinking how we can implement this when creating issues without the interactive mode, any ideas?

from jira-cli.

One temporal solution, if the project and issue type are provided and it has additional fields, enter into the interactive mode to ask for those required fields: jira create -p PK -t bug -m "My issue name" (ask for the required fields interactively) what do you think?

from jira-cli.

Maybe provide a "generic" flag where you could pass some kind of set of key value pairs for the additional fields, maybe just a plain old JSON object (which would be cleaner to parse, but might be harder to type). I don't know about the flag parsing library you are using, but if you are allowed to repeat flags, you could do like -c "key: value" -c "key2: value2" to allow for multiple fields to be input.

The "go-to-interactive" thing seems like a decent stopgap, but looses some of the power you get to automate things when you have everything as a flag.

from jira-cli.

@allout58 that sounds good, and it's supported by commander, now I'm thinking about the data type, is it always text?

from jira-cli.