Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Create Issue Partial ignoring issue type field

api

A routine I wrote a year or two back to create issues with Create Issue Partial recently started failing to set the issue type. It uses the IssueTypeID element with a value that's a valid type ID for the project (and which can be set in the UI); however, Gemini always saves with the default type value instead.

Is this functionality just broken (maybe 4.0 problem?), has something changed that's not documented, or am I simply going crazy and have been doing it wrong all along?

As an example, here's the XML for a request I tried a few minutes ago:

<IssueEN>
    <ProjectID>42</ProjectID>
    <IssueSummary>Release task: NT 2011-04-07 SR</IssueSummary>
    <IssueLongDesc>Release task for version &lt;b&gt;NT 2011-04-07 SR&lt;/b&gt;</IssueLongDesc>
    <ReportedBy>36</ReportedBy>
    <IssueTypeID>14</IssueTypeID>
    <IssueResolution>1</IssueResolution>
    <Components><IssueComponentEN><ComponentID>607</ComponentID></IssueComponentEN></Components>
    <IssuePriority>7</IssuePriority>
    <IssueSeverity>6</IssueSeverity>
    <IssueResources><IssueResourceEN><UserID>25</UserID></IssueResourceEN></IssueResources>
</IssueEN>

Gem created the issue just fine, but it set the issue type to 11 (the project default) and returned the same in the response. And again, 14 is valid for the project: I can go to the new issue in the UI and set it myself.
Bob W.
· 1 		Bob W.
Monday, April 4, 2011, 10:35:04 PM
Replies (3)
helpful
0
not helpful

Bob,

<IssueType>14</IssueType>

Lose the "ID" suffix from the XML tag name?

··· ok, I was wrong - Harvey is right :-)Dave LongTuesday, April 5, 2011, 11:58:53 AM
Harvey Kandola
· 212 		Harvey Kandola
Tuesday, April 5, 2011, 11:34:44 AM
helpful
0
not helpful

Hi Bob

This may have something to do with the Screens or Permissions.

If you are unable to set the Issue Type on the Create Stage Screen, then the Web Service may be defaulting it because of this. Alternatively, if the user you are connecting to the Web Service with, does not have the required "Permission", it may revert to the default.

these are just options to check out, and I will give these a bash myself to see if I can re-produce this behaviour, but I recon it's something along those lines.

Dave
Dave Long
· 1 		Dave Long
Tuesday, April 5, 2011, 11:37:32 AM
helpful
0
not helpful
ANSWER

Well, that was just silly. Removing 'ID' from the tag worked - not sure what happened there. But thanks!
Bob W.
· 1 		Bob W.
Tuesday, April 5, 2011, 5:37:49 PM