-
-
Notifications
You must be signed in to change notification settings - Fork 473
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
Missing fields in FixVersion struct #208
Comments
Pull Request #181 seems to be related to my problem, but has not seen activity in a while, and seems to break the API (which could be avoided easily). |
@urld I asked for a small change in the PR to maintain backward compatibility. It seems the PR author may have abandoned the issue, not sure. If you want to submit a backward compatible PR, I'd be happy to merge it and close the other one. |
urld
added a commit
to urld/go-jira
that referenced
this issue
Apr 28, 2019
The FixVersion type was missing some fields. Now it just aliases the more complete Version struct. Fixes andygrunwald#208
urld
added a commit
to urld/go-jira
that referenced
this issue
Apr 28, 2019
The FixVersion type was missing some fields. Now it just aliases the more complete Version struct. Fixes andygrunwald#208
urld
added a commit
to urld/go-jira
that referenced
this issue
Apr 28, 2019
The FixVersion type was missing some fields. Now it is a complete copy of the more complete Version struct, with the only difference thet the bool fields are pointers (for compatibility reasons). Fixes andygrunwald#208
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there any reason the fields of the struct representing a fixVersion of an issue, do not match the fields of the struct representing a projects version?
I can live with the bool pointer weirdness, but i'd really like to access the versions description directly from the issue.
If this is just an oversight, i could send a pull request adding the missing fields to .
The text was updated successfully, but these errors were encountered: