orastor / jira-client Goto Github PK

Please see here https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/
It does not work anymore with Jira 8.4+ because the URL format has been changed.

When reporter field is set as mandatory in Jira, it is not possible to create issues unless you specify that field

https://github.com/oRastor/jira-client/blob/master/src/Resource/Field.php#L34

Add a new field "reporter" as a constant class

Thanks for your help ;)

Searching on the "fixVersions" field does not work, because there is no fixVersions resource implemented.

It would be great it it would be added.

from what i can see, AuthorResource was only included in the initial commit and then removed. the Comment Resource still refers to it.

I can't include your package because Guzzle 6 is in use by other libraries installed on my system.

Jira plugins are able to add new field types in which case this library can't be used to manage issues with those custom field types.

Would it be possible to allow to extend the existing field types (e.g. by specifying a callback which is then called before doing the mapping in Field:: getSaveValue())? Simply extending the Field class does not work for me as this also means I have to modify any class creating new instances of the Field class to use my own Field class.

See: https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-basic-auth-and-cookie-based-auth/

As of March 15, 2018, in accordance to the Atlassian REST API Policy, support for passwords in HTTP basic auth requests will no longer be supported on or after September 15, 2018.

Instead of passwords, you should start using API tokens.

As far as I can see it is not possible to create remote links with this API client, right?

The following JSON posted to "/rest/api/latest/issue/${ISSUE}/remotelink" would create a remote link (Web Link):

{
    "object": {
        "url": "https://github.com/oRastor/jira-client",
        "title" : "Title of the link"
    }
}

See https://community.atlassian.com/t5/Answers-Developer-Questions/Create-hyperlink-in-Jira-issue-via-REST-API/qaq-p/552251#M89911

Adding a custom field which is of type "option-with-child" does not work with the current version of this library.

Example code:

$fluentIssueCreate->customField("12345", array("value" => "Foo", "child" => array("value" => "Bar")));

This worked till an update to JIRA 7.x as the previous JIRA version seem to used something else than "option-with-child" as field type.