Closed GoogleCodeExporter closed 9 years ago
This may be caused by one or more 'required' fields that do not match with the
current defaults. This is
a known limitation and, like all thinks, will eventually be added.
To fix this in the near-term I'm afraid you're going to need to crack the code
and provide those field
values.
Take a look at the following source file:
http://code.google.com/p/csharptest-net/source/browse/trunk/src/Tools/SvnPlugin/
JiraConnection.cs
Starting around line 232 you should find:
if (StringComparer.OrdinalIgnoreCase.Equals("Resolution", field.name))
param.values = new string[] { FindFixResolution() };
else if (StringComparer.OrdinalIgnoreCase.Equals("Assignee", field.name))
param.values = new string[] { assignTo.Id };
else
param.values = issue.GetFieldValue(paramName);
Just add your own logic here to populate those required fields.
Original comment by Grig...@gmail.com
on 22 Feb 2010 at 12:07
Original comment by Grig...@gmail.com
on 14 Sep 2010 at 1:34
Original comment by Grig...@gmail.com
on 14 Sep 2010 at 1:35
As of the lastest code on https://github.com/csharptest/JiraSVN
Custom Fields - You may now hard-code the value for any required custom field
in jira by specifying both the action and field name seperated by a ':'. thus
to set customfield_10030 to the value 'true' for the 'Resolve' action you would
specify the following:
<add key="Resolve:customfield_10030" value="true"/>
Original comment by Grig...@gmail.com
on 26 Jan 2011 at 11:21
Original issue reported on code.google.com by
goo...@hardcoded.de
on 10 Dec 2009 at 2:40