-
Bug
-
Resolution: Not a bug
-
Medium (View bug fix roadmap)
-
None
-
3.7.2, 3.7.3, 3.7.4
-
None
-
3.07
-
The following PERL script works for fixVersions but NOT affectsVersions:
my $jiraToken = XMLRPC::Lite->proxy('http://jira.atlassian.com/rpc/xmlrpc');
my $authToken = $jiraToken->call( "jira1.login", $user, $pass )->result();
my $call = $jiraToken->call("jira1.updateIssue", $authToken, "TST-9485",
{
"fixVersions" => [SOAP::Data->type(string => "10330")]
}
);
$jiraToken->call("jira1.logout", $authToken);
The same code but specifying affectsVersions:
my $jiraToken = XMLRPC::Lite->proxy('http://jira.atlassian.com/rpc/xmlrpc');
my $authToken = $jiraToken->call( "jira1.login", $user, $pass )->result();
my $call = $jiraToken->call("jira1.updateIssue", $authToken, "TST-9485",
{
"affectsVersions" => [SOAP::Data->type(string => "10330")]
}
);
$jiraToken->call("jira1.logout", $authToken);
Note: The same issue occurs using the equivalent SOAP calls in PERL.
- is caused by
-
JRASERVER-8717 retention of field values when using SOAP
- Closed
[JRASERVER-12300] affectsVersion field cannot be updated via SOAP or XMLRPC
Hi James,
Sorry for the delay in responding.
You are right the name of fields are a bit confusing. You need to use the values that are defined as constants in:
http://www.atlassian.com/software/jira/docs/api/latest/com/atlassian/jira/issue/IssueFieldConstants.html
Unfortunately changing them would be hard without breaking backwards compatibility. Therefore the solution is not
really a "work around".
I will resolve this issue for now. Actually the best place to ask developer related questions for JIRA is the JIRA Dev forum:
http://forums.atlassian.com/forum.jspa?forumID=100
Thanks,
Anton
Yes - the workaround did the trick! Should status of this issue be updated to "Open" then?
Yuen-Chi Lian [Atlassian]
added a comment - Taking a look at the source code found that an Orderable field will be updated if the provided RemoteFieldValue's Id matches with its Id, i.e. in UpdateFieldsHelperBeanImpl:
final OrderableField orderableField = fieldScreenRenderLayoutItem.getOrderableField(); if (actionParams.containsKey(orderableField.getId())) { // ...
Therefore, to get around this, you will have to use "versions" (see IssueFieldConstants.AFFECTED_VERSIONS), e.g.
my $updatedIssue = $soap->updateIssue($auth->result(), $issue->result()->{key}, [
{"id" => SOAP::Data->type(string => "fixVersions"),
"values" => [SOAP::Data->type(string => "10002")]
},
{"id" => SOAP::Data->type(string => "versions"), # not "affectsVersions"
"values" => [SOAP::Data->type(string => "10002")]
}
]);
Cheers,
Yuen-Chi Lian
Yuen-Chi Lian [Atlassian]
added a comment - Taking a look at the source code found that an Orderable field will be updated if the provided RemoteFieldValue 's Id matches with its Id , i.e. in UpdateFieldsHelperBeanImpl :
final OrderableField orderableField = fieldScreenRenderLayoutItem.getOrderableField();
if (actionParams.containsKey(orderableField.getId()))
{ // ...
Therefore, to get around this, you will have to use "versions" (see IssueFieldConstants.AFFECTED_VERSIONS ), e.g.
my $updatedIssue = $soap->updateIssue($auth->result(), $issue->result()->{key}, [
{ "id" => SOAP::Data->type(string => "fixVersions" ),
"values" => [SOAP::Data->type(string => "10002" )]
},
{ "id" => SOAP::Data->type(string => "versions" ), # not "affectsVersions"
"values" => [SOAP::Data->type(string => "10002" )]
}
]);
Cheers,
Yuen-Chi Lian
I wonder if there's any way to give a field two names (from updateIssue's perspective) so you can preserve backwards compatibility but still make incoming and outgoing soap transactions match.