<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: How much can we re-name basic terms without affecting functionality? (Thread)</title><description>  Is it possible to edit the display name of basic terms, ie can we change these to our bespoke in-house terms?  For example, renaming 'Test Set' as 'Test Suite', so that it appears as such in the menu. I don't want to affect behind-the-scenes functionality, and I'm only really talking about menu items, but I expect there's only a small degree of customisation possible?  It's not such a crazy question! The reason I ask is that if we propose adopting SpiraTeam across our wider organisation, there will need to be a "re-education" of some potential users and a bit of retro-fit to work with existing practices and terms. If we can absorb some reticence elsehwere, then roll-out will be better received and future take-up prospects greater. </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/109.aspx</link><item><guid isPermaLink="false">threadId=109</guid><author>Andy Smith (andy.smith@infoterra-global.com)</author><title>How much can we re-name basic terms without affecting functionality?</title><description>  Is it possible to edit the display name of basic terms, ie can we change these to our bespoke in-house terms?  For example, renaming 'Test Set' as 'Test Suite', so that it appears as such in the menu. I don't want to affect behind-the-scenes functionality, and I'm only really talking about menu items, but I expect there's only a small degree of customisation possible?  It's not such a crazy question! The reason I ask is that if we propose adopting SpiraTeam across our wider organisation, there will need to be a "re-education" of some potential users and a bit of retro-fit to work with existing practices and terms. If we can absorb some reticence elsehwere, then roll-out will be better received and future take-up prospects greater. </description><pubDate>Wed, 06 Jul 2011 11:26:48 -0400</pubDate><a10:updated>2011-07-07T11:41:03-04:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/109.aspx</link></item><item><guid isPermaLink="false">messageId=216</guid><author>David J (adam.sandman+support@inflectra.com)</author><title> Actually if you are using v3.1 this is very easy and won't break anything. We localized SpiraTeam i</title><description> Actually if you are using v3.1 this is very easy and won't break anything. We localized SpiraTeam in v3.1 to support multiple languages, so you can simply modify the .resx resource files in the App_GlobalResources folder to change some of the terminology. </description><pubDate>Wed, 06 Jul 2011 19:01:26 -0400</pubDate><a10:updated>2011-07-06T19:01:26-04:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/109.aspx#reply216</link></item><item><guid isPermaLink="false">messageId=218</guid><author>Andy Smith (andy.smith@infoterra-global.com)</author><title>Bravo!  Many thanks.     </title><description>Bravo!  Many thanks.     </description><pubDate>Thu, 07 Jul 2011 11:41:03 -0400</pubDate><a10:updated>2011-07-07T11:41:03-04:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/109.aspx#reply218</link></item></channel></rss>