Hi All, In SpiraTeam release 4.2 the Requirement Type has a default values of Feature, Need, Package (Quality, Use Case, User Story), and for the hosted customer we can't modify these values. I'd like to be more concise on the requirement types, I could create new Custom Properties to specify Theme, Epic, User Story and label them as Classification for example. But that seems to be redundant of what out-of-the box intention of the Requirement Type. Is there any reasons why we can't edit the default values, and a good workaround? en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/best-practices/1119.aspxthreadId=1119Ben Nguyenphu (ben.nguyenphu@hmhpub.com)customizationHi All, In SpiraTeam release 4.2 the Requirement Type has a default values of Feature, Need, Package (Quality, Use Case, User Story), and for the hosted customer we can't modify these values. I'd like to be more concise on the requirement types, I could create new Custom Properties to specify Theme, Epic, User Story and label them as Classification for example. But that seems to be redundant of what out-of-the box intention of the Requirement Type. Is there any reasons why we can't edit the default values, and a good workaround? Mon, 22 Dec 2014 19:27:46 -05002017-12-12T16:06:19-05:00/Support/Forum/spirateam/best-practices/1119.aspxmessageId=1990Jim R (donotreply5@kronodesk.net) Hi Ben Those fields are not currently editable for either hosted or on-premise customers, we do have plans to make them so in v5.0 in 2015. Also in terms of Epic, Theme, etc. those are really meant to be served in other ways, please take a look at: https://www.inflectra.com/SpiraTeam/Methodologies/Agile-Development.aspx at the bottom is a table: SpiraTeam Extreme Programming Scrum AgileUP / DSDM Summary Requirement Epic Epic Feature Group Requirement User Story Backlog Item Requirement Task Task Task Task Release Release Release Release Iteration Iteration Sprint Iteration Test Case Acceptance Test Acceptance Test Test Scenario Regards Jim Wed, 24 Dec 2014 13:38:16 -05002014-12-24T13:38:16-05:00/Support/Forum/spirateam/best-practices/1119.aspx#reply1990messageId=2893willy T Tongent (willy.tongen@equitybank.co.ke)Hi, Version 5.0 (Spirateam) is released but we still cannot edit "requirement types". Was the plan to make it customizable dropped? Regards Thu, 02 Feb 2017 09:09:38 -05002017-02-02T09:09:38-05:00/Support/Forum/spirateam/best-practices/1119.aspx#reply2893messageId=2894Kat A (elise.brooks@inflectra.com) Hi Willy, Sorry, yes, the scope of 5.0 changed. SpiraTeam does not have the ability to customize requirement types yet. That feature is still planned, but I don't know for which version. Regards, Elise Thu, 02 Feb 2017 15:34:43 -05002017-02-02T15:34:43-05:00/Support/Forum/spirateam/best-practices/1119.aspx#reply2894messageId=3042Neil Findlay (neil.findlay@bjss.co.uk) Hello, any idea when this functionality is going to be available. I see the need to customise requirement types as key functionality for a test management system, and although we have a workaround in place - its clunky. Any ideas, if this is on your product roadmap? if so in what version? Thanks in advance Neil. Wed, 21 Jun 2017 09:52:18 -04002017-06-21T09:52:18-04:00/Support/Forum/spirateam/best-practices/1119.aspx#reply3042messageId=3185Neil Findlay (neil.findlay@bjss.co.uk) Any idea how long i need to wait to get a respond to a question on here? 6 months is pretty long in my opinion! Hello, anyone here?? Tue, 12 Dec 2017 16:06:18 -05002017-12-12T16:06:18-05:00/Support/Forum/spirateam/best-practices/1119.aspx#reply3185