Hello There are several items that would help make the Requirements import from EnterpriseArchitet (EA) into SpiraTest (ST) much more useful than it currently is. Grouping requirements under packages in EA ought to be imported as Requirements (Package) and child requirements. As it is, it means a ton of 'massaging' of the requirements in SpiraTest into an appropriate hierarchy. Improve the field mapping between EA & ST so that users can map any field in the requirement AND tagged values as well. At the moment only the Name, Description, Importance & Author are imported which, again, requires a ton of massaging of the requirements list. In EA's Project Browser it is possible to create parent > child requirement relationships ... it would be helpful if this parent > child relationship was also imported correctly to ST ... at the moment only the Parent is imported In EA there is a 'parent' req. "Data Fields" with 3 children of Handle Time, Incident ID, Interaction ID ... only the Parent 'Data Fields' was imported into ST A much closer integration between ST & EA would make using both these tools a lot more enjoyable as well as useful. Otherwise I end having to spend too much time 'fixing' data between the two applications trying to keep the requirements information & hierarchy up to date. 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/integrations/importers/399.aspxthreadId=399Jonathan Chandler (jonathan.chandler@kineticit.com.au) Hello There are several items that would help make the Requirements import from EnterpriseArchitet (EA) into SpiraTest (ST) much more useful than it currently is. Grouping requirements under packages in EA ought to be imported as Requirements (Package) and child requirements. As it is, it means a ton of 'massaging' of the requirements in SpiraTest into an appropriate hierarchy. Improve the field mapping between EA & ST so that users can map any field in the requirement AND tagged values as well. At the moment only the Name, Description, Importance & Author are imported which, again, requires a ton of massaging of the requirements list. In EA's Project Browser it is possible to create parent > child requirement relationships ... it would be helpful if this parent > child relationship was also imported correctly to ST ... at the moment only the Parent is imported In EA there is a 'parent' req. "Data Fields" with 3 children of Handle Time, Incident ID, Interaction ID ... only the Parent 'Data Fields' was imported into ST A much closer integration between ST & EA would make using both these tools a lot more enjoyable as well as useful. Otherwise I end having to spend too much time 'fixing' data between the two applications trying to keep the requirements information & hierarchy up to date. Wed, 17 Oct 2012 07:27:00 -04002012-11-05T01:14:52-05:00/Support/Forum/integrations/importers/399.aspxmessageId=754David J (adam.sandman+support@inflectra.com) Hi Jonathan Thanks so much for the feedback on our EA integration with SpiraTest, I have logged this as an enhancement suggestion for the system. Regards Adam Wed, 17 Oct 2012 17:14:22 -04002012-10-17T17:14:22-04:00/Support/Forum/integrations/importers/399.aspx#reply754messageId=784Jonathan Chandler (jonathan.chandler@kineticit.com.au) Hi Adam Would it be possible to interface with Rational Requirement Composer as well? http://www-142.ibm.com/software/products/au/en/rrc This RCC suits software requirements rather than DOORs - I checked with IBM, DOORs is more orientated towards construction / building (statement from IBM support). Cheers J Mon, 05 Nov 2012 01:14:52 -05002012-11-05T01:14:52-05:00/Support/Forum/integrations/importers/399.aspx#reply784