<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: Copying requirements does not copy custom properties (Thread)</title><description>When I using Tools &gt; Export to copy requirements from one project to another, the values of the custom properties are not copied across?</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/spirateam/issues-questions/8.aspx</link><item><guid isPermaLink="false">threadId=8</guid><author>Steve M (mike.morrey+support@inflectra.com)</author><title>Copying requirements does not copy custom properties</title><description>When I using Tools &gt; Export to copy requirements from one project to another, the values of the custom properties are not copied across?</description><pubDate>Mon, 07 Feb 2011 19:26:30 -0500</pubDate><a10:updated>2011-03-10T15:13:11-05:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/8.aspx</link></item><item><guid isPermaLink="false">messageId=8</guid><author>Steve M (mike.morrey+support@inflectra.com)</author><title>Unfortunately because custom properties are set per-project the system is not able to copy these val</title><description>Unfortunately because custom properties are set per-project the system is not able to copy these values across when you copy a requirement from one project to another. This is a limitation in the system.</description><pubDate>Mon, 07 Feb 2011 19:27:14 -0500</pubDate><a10:updated>2011-02-07T19:27:14-05:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/8.aspx#reply8</link></item><item><guid isPermaLink="false">messageId=41</guid><author>Thomas Hartmann (thomas.hartmann@ubidyne.com)</author><title>I had the same problem in the past and you mention that this is a limitation. Is there probably a pl</title><description>I had the same problem in the past and you mention that this is a limitation. Is there probably a plan to remove this limitation in future ?</description><pubDate>Thu, 10 Mar 2011 15:09:51 -0500</pubDate><a10:updated>2011-03-10T15:09:51-05:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/8.aspx#reply41</link></item><item><guid isPermaLink="false">messageId=42</guid><author>Steve M (mike.morrey+support@inflectra.com)</author><title>  It is something on our list, but at the moment it's a little ways down. The biggest issue is that </title><description>  It is something on our list, but at the moment it's a little ways down. The biggest issue is that a whole system of cross-referencing would have to be implemented. i.e. You would have to define that "list 1" in project 'A' is the same as "list D" in project 'B', and then map all the values in "list 1" to "list D". Because each project can have it's own list definitions, our developers don't want to 'assume' that you wish to overwrite existing list definitions and values, etc.     </description><pubDate>Thu, 10 Mar 2011 15:13:11 -0500</pubDate><a10:updated>2011-03-10T15:13:11-05:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/8.aspx#reply42</link></item></channel></rss>