Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unable to create issue due to additional required fields
See original GitHub issueWhat it should do
Find required fields, and allow inputting required ones
What it does
Fails to create a new issue because some fields are required for new issues on our Jira projects.
Other Info
After looking into the Jira API a bit, the expand query string can be set to get all fields on an issue type. However, with many projects this can be massive. I would suggest waiting to fetch a more detailed set of metadata until after the user has selected the project at the very least, maybe even better to wait until they have selected the type. The request can then be filtered down by project name and issue type to limit the returned data (see https://docs.atlassian.com/software/jira/docs/api/REST/8.1.2/#api/2/issue-getCreateIssueMeta)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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.
@allout58 that sounds good, and it’s supported by commander, now I’m thinking about the data type, is it always text?