<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: How to move requirement using soap api functions (Thread)</title><description>&#xD;
Hi&#xD;
&#xD;
    I am trying to move requirements using functions from spiratest soap api. Using the Requirement_Move function I need to specify the destination id.      Here is an example of requirements which I may have     Req1  Req2  Req3  Req4    Req5    Req6    Req7  Req8     So 5, 6 and 7 are sub features of 4. So what I need to be able to do is to move for example Req7 to be under Req1 or move Req2 under Req4.     How can I do this?? It doesn't seem possible using the soap api.        if I select the destination id to be for example Req4, then the requirement is moved to the same level as req4 which is of no use.      Thanks for you time     Michael </description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spiratest/issues-questions/886.aspx</link><item><guid isPermaLink="false">threadId=886</guid><author>Michael Long (michaellong77@gmail.com)</author><category domain="http://www.inflectra.com/kronodesk/thread/tag">soap</category><category domain="http://www.inflectra.com/kronodesk/thread/tag"> api</category><title>How to move requirement using soap api functions</title><description>&#xD;
Hi&#xD;
&#xD;
    I am trying to move requirements using functions from spiratest soap api. Using the Requirement_Move function I need to specify the destination id.      Here is an example of requirements which I may have     Req1  Req2  Req3  Req4    Req5    Req6    Req7  Req8     So 5, 6 and 7 are sub features of 4. So what I need to be able to do is to move for example Req7 to be under Req1 or move Req2 under Req4.     How can I do this?? It doesn't seem possible using the soap api.        if I select the destination id to be for example Req4, then the requirement is moved to the same level as req4 which is of no use.      Thanks for you time     Michael </description><pubDate>Mon, 14 Apr 2014 08:21:42 -0400</pubDate><a10:updated>2014-05-09T07:25:53-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/886.aspx</link></item><item><guid isPermaLink="false">messageId=1617</guid><author>Inflectra Sarah (donotreply6@kronodesk.net)</author><title>&#xD;
Hi Michael&#xD;
&#xD;
    You are right the API doesn't allow that directly, it needs to have an existing </title><description>&#xD;
Hi Michael&#xD;
&#xD;
    You are right the API doesn't allow that directly, it needs to have an existing item already in the child branch. The plan in the future is to add Requirement_Indent and Requirement_Outdent API functions.     Regards   Sarah </description><pubDate>Thu, 17 Apr 2014 14:49:01 -0400</pubDate><a10:updated>2014-04-17T14:49:01-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/886.aspx#reply1617</link></item><item><guid isPermaLink="false">messageId=1640</guid><author>Michael Long (michaellong77@gmail.com)</author><title>The requirement_move doesn't make any sense to me. If you supply a destination id then why doesn't i</title><description>The requirement_move doesn't make any sense to me. If you supply a destination id then why doesn't it move the requirement under that item. That would be simple solution. And if you want the item on top level then you could just leave that parameter blank. That function is not usable at the moment.           </description><pubDate>Fri, 09 May 2014 07:25:53 -0400</pubDate><a10:updated>2014-05-09T07:25:53-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/886.aspx#reply1640</link></item></channel></rss>