The issue was being found by ID, but there are cases where a user will
have the issue key but not the ID, whereas if the user has the ID then
it's highly likely they have the key, because they probably got the ID
from the API, which would also return the key.
JIRA only allows issues to be created with certain fields set. This
means if a user needs to create an issue through the API with the
description set, they need to create the issue first, and then call the
API again to update it.
Without this commit, the way to do this through the package is by
calling IssueService.Create and then use the client's NewRequest method
to create a raw HTTP request for the Update. This isn't bad, but it can
be better.
JIRA supports SelectList field types, which are similar to but
represented not quite the same as Strings. This change allows go-jira
to create issues with custom fields on them that are SelectLists.
* 'master' of https://github.com/bidesh/go-jira:
Adds test for authentication on expected json. Adds test to metaissue
Removes check for statuscode as jiraclient already does it. Adds test for nonok status code returned
Adds test for GetProjectWithName and GetIssueTypeWithName
Omit more empty attributes when converting from struct to map
Adds unknown map for arbitrary fields in IssueFields. Adds Custom Marshall,Unmarshall. Adds structs tag where necessary
Adds metaissue support.
Completes the APi for session. Adds logout and GetCurrentUser
The Response struct has StartAt, MaxResults and Total fields, which are
returned from JIRA API in issue search responses. They are now
accessible in Response object.
