<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: Azure DevOp Syncing Issues (Thread)</title><description> We are using SpiraTest with Cloud Version of DevOps but we are having syncing issues or we either need to understand the platform better. Some of the issues are the following:  1. SpiraTest will overwrite changes made in DevOps for some reason (not sure why), it will change dev statuses or move to previous iteration path if a change is detected, this is automatic. Not in all cases.  2. Bugs cant be placed in actual backlog, we had to create a fake backlog iteration to place bugs not in a sprint. Reason why releases only show in Spiratest, but not backlog.  3. Bugs created in SpiraTest arent parented back to the original user story, we have to manually parent them back. Causing considering able time on our end. Anyway to resolve this?  </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/2117.aspx</link><item><guid isPermaLink="false">threadId=2117</guid><author>Sandeep Prasad (sandeep.prasad@spirit.com)</author><title>Azure DevOp Syncing Issues</title><description> We are using SpiraTest with Cloud Version of DevOps but we are having syncing issues or we either need to understand the platform better. Some of the issues are the following:  1. SpiraTest will overwrite changes made in DevOps for some reason (not sure why), it will change dev statuses or move to previous iteration path if a change is detected, this is automatic. Not in all cases.  2. Bugs cant be placed in actual backlog, we had to create a fake backlog iteration to place bugs not in a sprint. Reason why releases only show in Spiratest, but not backlog.  3. Bugs created in SpiraTest arent parented back to the original user story, we have to manually parent them back. Causing considering able time on our end. Anyway to resolve this?  </description><pubDate>Tue, 26 Nov 2019 21:51:27 -0500</pubDate><a10:updated>2019-11-26T22:14:04-05:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/2117.aspx</link></item><item><guid isPermaLink="false">messageId=3688</guid><author>David J (adam.sandman+support@inflectra.com)</author><title> Please could you send this as a  help desk ticket  instead.  The forums are for more general questi</title><description> Please could you send this as a  help desk ticket  instead.  The forums are for more general questions. Resolving customer specific issues is best done through our help desk.  In general, if you are running the sync in bidirectional mode, changes can be made in either direction.  Thanks  David </description><pubDate>Tue, 26 Nov 2019 22:14:04 -0500</pubDate><a10:updated>2019-11-26T22:14:04-05:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/2117.aspx#reply3688</link></item></channel></rss>