addIssue:Failure:JIRA Message: _empty_ => Field '' cannot be

[lancelyons]

We are configuring Jira integration using Jira REST api and are testing using the create issue in Testlink 1.9.14. We have a couple custom fields that are required so we have added those to the JIRA REST integration configuration.

The jira issuetracking configuration is set as follows.

<issuetracker>
<username>jirauser</username>
<password>jirapassword</password>
<uribase>https://jira.ourcompany.com</uribase>
<uriapi>https://jira.ourcompany.com/rest/api/2/</uriapi>
<uriview>https://jira.ourcompany.com/browse/</uriview>
<uricreate>https://jira.ourcompany.com/secure/Crea ... /uricreate>
<userinteraction>1</userinteraction>
<projectkey>NLO</projectkey>
<issuetype>10302</issuetype>
<attributes>
<customFieldValues>
<customField>
<customfieldId>customfield_15103</customfieldId>
<type>Select</type> <values><value>Testlink</value></values>
</customField>

<customField>
<customfieldId>customfield_16001</customfieldId>
<type>CascadingSelect</type> <values><value>Testlink</value></values>
</customField>

</customFieldValues>
</attributes>
</issuetracker>

When we do a create user and fill in the fields and hit save, we get the following error.


addIssue:Failure:JIRA Message: _empty_ => Field '' cannot be set. It is not on the appropriate screen, or unknown.

[lancelyons]

Some additional information about the issue above. If I make the 2 custom fields NOT REQUIRED and then comment out the attributes part of the issueintegration configuration, then the issue is created successfully.

If I create a brand new Jira project using Jira defaults, and use this project key for the create issue, then the issue is created ok without the attributes portion.

[dsommer]

Experiencing the same issue as of now, with version 1.9.16 Moka pot.

Opened an issue in Mantis related, if solution is provided, will update here.

Our configuration follows the one on closed ticket http://mantis.testlink.org/print_bug_pa ... ug_id=7050

Tried different changes and data types, but JIRA always responds same failure message.