If you use Jira Cloud plese read all of this note.

The files in this location are a development build patch to P4DTG 2018.1 for job101543.

This bug may affect Jira Cloud and on-premise Jira installations.  This bug stops all replication.

When 2018.1 is patched you should install use that.

Sample errors in the logs (log-MAPNAME.log or jira-rest-NNNNNN.log.N):

Feb 24, 2020 11:08:45 AM com.perforce.p4dtg.plugin.jira.tcp.internal.request.RequestHandler queryDefects
SEVERE: RestClientException{statusCode=Optional.absent(), errorCollections=[]}

or

Caused by: org.codehaus.jettison.json.JSONException: JSONObject["name"] not found.

or

INFO: RestClientException in hasProjectAccess("CDS"): org.codehaus.jettison.json.JSONException: JSONObject["names"] not found.
RestClientException{statusCode=Optional.absent(), errorCollections=[]}

---------------------------------------

To deploy:

This build requires java 1.8 or later.

Save these two files somewhere else as we're going to replace them.

  <p4dtg-install>/jira/jira-rest.jar
  <p4dtg-install>/jira/jira-rest-all-dependencies.jar

Stop replication

Replace the two jar files in the jira subdirectory

Assure the file protections allow read and execute of these two jars.

Start replication

---------------------------------------

Notes for Jira's Assignee and Reporter:

Jira Cloud does not have a "user name" like Jira on premises does so P4DTG 2018.1 could not replicate Jira's
Assignee and Reporter.

This patch can retrieve user alternate identifiers:  email, short email (before "@"), or Display name.

IMPORTANT NOTE:  Jira Cloud Account security can limit the plugin's access to your email.
Individuals control access to their account's email in their Jira Account settings.
If you find your Display Name is replicated, security is the likely cause.

The replicated User information attempts to find a value.
The default fields we check are:  "name,email,emailshort,displayname" which works for both Jira 
on premises and Jira Cloud.

To change the ordering, add a <UserStyle> element to jira-rest-config.xml.
Sample:
<Config>
  <JiraHandling>
      <UserStyle>name,emailshort,email,displayname</UserStyle>
  </JiraHandling>