-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
meta data is not populated for jira create
#123
Comments
Confirmed that adding |
If simpletons like myself get here, to get this to work, as @udryan10 suggested, put the following into
rebuild and profit. |
I'm also hitting this issue, which is resulting in The short version is that it appears that the behavior of slipscheme (used to generate the files in jiradata) changed since the last released version and so And the longer version (which ended up way longer than I intended): From what I could see initially, the issue appeared to be that However, it appears that the files in jiradata/ are all autogenerated, and manually tweaking things until they worked didn't seem like the right fix, so I tried running From what I can see, when the jiradata files are generated using the latest master of slipscheme, there is a naming conflict for the IssueType type, which is generated from both It looks like, if slipscheme is changed so that it creates CreateMetaIssueType instead of just IssueType when processing the CreateMeta schema, then the jiradata files are regenerated and type errors fixed, that would fix the issue while still having the jiradata files able to be autogenerated. |
I have merged in PR#127 to add the Thanks all for looking into this. |
I see the full json (with fields and allowedValues) coming back from the
jira createmeta
request (with-v -v -v
, but it doesn't translate into the output. Looking at it a little, it seems that jiradata/IssueType.go doesn't have Fields defined. Do I need to update the schema somehow? Maybe running schemas/fetch-schemas.py against my instance of Jira? I can send more debug information if desired.The text was updated successfully, but these errors were encountered: