Home

SpiraTest External Bug Tracking Integration Guide

Contents

1. If you already see an entry for BugzillaDataSync you should click on its Edit link If you don t see such an entry in the list please click on the Add button instead In either case you will be taken to the following screen where you can enter or modify the Bugzilla Data Synchronization plug in Edit Plug in BugzillaDataSync lt lt Back to Data Synchronization Home Please enter edit the following information for the plug in The exact information that needs to be entered Is specific to each plug in and you should refer to the documentation for the plug in when entering changing it Name BugzillaDataSync Description This plug in allows incidents in the system to be synchronized with the Bugzilla bug tracking system Connection Info http landfill bugzilla org bugzilla 3 0 branch xmlrpe cgi Login bugzillauser mycompany com Password Time Offset Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 You need to fill out the following fields for the Bugzilla Plug in to operate correctly Name this needs to be set to BugzillaDataSync This needs to match the name of the plug in DLL assembly that was copied into the C Program Files SpiraTeam Bin folder minus the dll file extension If you renamed the BugzillaDataSync dll file for any reason then you need to change the name here to match Description this should be set to a description of the plug in This is an optional field that
2. hyperlink next to the TFS plug in name This will take you to the data mapping home page for the currently selected project Ms TfsDataSync Project Data Mapping TFS Test Project 1 Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the MsTfsDataSync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name TFS Test Project 1 External Key Test Project 1 Active Yes T Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Requirement mportance status Test Case Pronty Incident Pronty Severity Status Type Release Task Pronty status If the project name does not match the name of the project you want to configure the data mapping for click on the Change Project hyperlink to change the current project To enable this project for data synchronization with TFS you need to enter gt External Key This should be set to the name of the project in TFS as visible from the Visual Studio Team Explorer ee rr Library Information System 2 H Lj Work Items C Documents e C Reports e C Builds 5 Source Control gt Active Flag Set thi
3. lt setting gt lt setting name Login serializeAs String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name Password serializeAs String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name EventLogSource serializeAs String gt lt value gt SpiraTeam Data Sync Service lt value gt lt setting gt lt setting name TraceLogging serializeAs String gt lt value gt False lt value gt lt setting gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt applicationSettings gt lt configuration gt The sections that need to be verified and possibly changed are marked in yellow above You need to check the following information gt The polling interval allows you to specify how frequently the data synchronization service will ask Spiraleam and the external system for new data updates The value is specified in milliseconds and we recommend a value no smaller than 5 minutes i e 300 000ms The larger the number the longer it will take for data to be synchronized but the lower the network and server overhead gt The base URL to your instance SpiraTeam It is typically of the form http lt server name gt SpiraTeam Make sure that when you enter this URL on a browser on the server itself the application login page appears gt A valid login name and password to your instance of SpiraTeam This user needs to be a member of the project s tha
4. 2 Resolved Fixed 3 __ Resolved Not Reproducible 4 Resolved Duplicate 5 Resolved Postponed 6 Resolved Won t Fi Resolved By Design 8 Resolved Implemented 9 Resolved Won t Implement Resolved Won t Respond Resolved Waiting For Info Resolved Completed Resolved Canceled In addition to these statuses FogBugz also has the concept of a Closed case which is one where the case has been assigned to the special Closed user user id 1 If you want to map a SpiraTeam status to this special closed status for the external key just enter Closed instead of a numeric ID and that will tell the plug in to associate that SpiraTest status with the special condition of a FogBugz case that is assigned to the closed user c Incident Priority Click on the Priority hyperlink under Incident Standard Fields to bring up the Incident Priority mapping configuration screen 1 Must Fix 7 a 2 Must Fix 7 3 Must Fix 4 Fix lf Time JE a 5 Fix If Time H x 6 Fix If Time H lt lt fn w T Don t Fix The table lists each of the incident priorities available in SpiraTeam and provides you with the ability to enter the matching FogBugz priority ID for each one You can map multiple SpiraTeam fields to the same FogBugz fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on t
5. 2 High Yes 3 Medium 4 Low The table lists each of the task priorities available in SpiraTeam and provides you with the ability to enter the matching TFS priority value for each one 5 2 7 Configuring the Task Custom Property Mapping Now that the various SpiraTeam standard task fields have been mapped correctly we need to configure the custom property mappings This is used for both custom properties in SpiraTeam that map to custom fields in TFS and also for custom properties in SpiraTeam that are used to map to standard fields in TFS e g Area that don t exist in SpiraTeam From the View Edit Project Data Mapping screen you need to click on the name of the Task Custom Property that you want to add data mapping information for Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Requirement Importance Status Test Case Prionty Incident Pnonty Severity k Rank Status Release Task a TFS s Area Field First you need to go to Administration gt Edit Custom Lists and create a new custom list that contains all the different Areas that are being used in TFS Then you need to go to Administration gt Edit Custom Properties and add a new ist custom property onto the Task artifact type called Area and link it to the Area custom list you created in the previous step T
6. Cashias a cmeneke ias ha han am ba bie eae Status Started Started Started Started Started Started Starbed Started Started Startup Type Automatic Automatic Automatic Aitomatic Manual Marual Manual Manwal Manual Log On As Local System Local Syster Local System Local System Local System Local Service Local System Local System Local Systern Local Service Local Systern Local System Local Systeri Local Service Local Systeri lasal O bam synchronization continues between SpiraTeam and JIRA after a reboot of the server 3 3 2 Using SpiraTeam with JIRA Now that the integration service has been configured and the service started initially any incidents created in SpiraTeam for the specified projects will be imported into JIRA and if using JIRA 4 x any existing issues in JIRA will get loaded into SpiraTeam At this point we recommend opening the Windows Event Viewer and choosing the Application Log In this log any error messages raised by the SpiraTeam Data Sync Service will be displayed If you see any error messages at this point we recommend immediately stopping the SpiraTeam service and checking the various mapping entries If you cannot see any issues with the mapping information we recommend sending a copy of the event log message s to Inflectra customer services Support inflectra com who will help you troubleshoot the problem To use SpiralTeam with JIRA on an ongoing basis we recom
7. Click on the Status hyperlink under Requirement Standard Fields to bring up the Requirement status mapping configuration screen Edit Standard Field Data Mapping TFS Test Project 1 Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the MsTisDataSync plug in next to each SpiraTeam value Field Value Active External Key Primary Accepted Yes Accepted bi Completed Yes Closed i saan Yes Design noes lec Removed Planned Ready o Rejected Rejected Requested New EEI EIEI eI E A A A A A A pa th a The table lists each of the requirement statuses available in SpiraTeam and provides you with the ability to enter the matching TFS work item State for each one Unlike the mapping for incidents see above Spiraleam does not track the reason codes associated with the requirements in MS TFS so you only need to map the State names from TFS with the requirement status names You can map multiple SpiraTeam fields to the same TFS fields in which case only one of the values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from TFS gt SpiraTeam b Requirement Importance Click on the Importance hyperlink under Requirement Standard Fields to bring up the Requirement Importance mapping configuration screen 1 Critical 2 High 3 Medium 4 Low The table lists each
8. High 3 Medium 4 Low Unlike the other incident standard fields JIRA doesn t actually have a built in field for storing the severity of an issue so if you want to be able to see the SpiraTeam incident severity in JIRA you ll need to create a JIRA custom list field to store the different severity values If you don t want to synchronize severity values with JIRA you can skip the rest of this section Once you have created a custom field in JIRA to contain the list of severity values you need to now populate the above table with the name Not the ID of the severity custom property values inside JIRA and click Update Secondly you need to go to the Plug in configuration screen Edit Plug in JiraDataSync lt lt Back to Data Synchronization Home Please enter edit the following information for the plug in The exact information that needs to be entered is specific to each plug in and you should refer to the documentation for the plug in when entering changing it Name JiraDataSync Description This plug in allows incidents in the system to be synchronized with the JIRA issue tracking system Connection Info Login Password Time Offset C Auto Map Users Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 On this screen you need to enter the ID of the custom field that you re using to store severities in JIRA and populate the Custom 01 property with this value see above The ID can be found by lo
9. Name JiraDataSync Description This plug in allows incidents in the system to be synchronized with the JIRA issue tracking system Connection fhtpidalek808000 ees Info cals syncuser O o O Aiia ee Time Offset o T Auto Map Users Custom 01 Custom 02 Custom 03 Custom 04 G Custom 05 Related o You need to fill out the following fields for the JIRA Plug in to operate correctly gt Name this needs to be set to JiraDataSync This needs to match the name of the plug in DLL assembly that was copied into the C Program Files SpiraTeam Bin folder minus the dll file extension If you renamed the JiraDataSync dll file for any reason then you need to change the name here to match gt Description this should be set to a description of the plug in This is an optional field that is used for documentation purposes and is not actually used by the system Connection Info this should the full URL to the JIRA installation being connected to including any custom port numbers Entering this URL into a web browser should bring up the JIRA login page Login this should be set to a valid login to the JIRA installation The login needs to have permissions to create and view issues and versions within JIRA Password this should be set to the password of the login specified above Time Offset normally this should be set to zero but if you find that issues being changed in JIRA are
10. that is used to store the mapped external identifier for the equivalent Version in Redmine You need to enter the numeric ID of the equivalent version in Redmine enter it into this text box and click Save You should now repeat for all the other releases and iterations in the project In addition any Versions that have already been created in Redmine will be automatically imported into SpiraTeam if they do not already exist in SpiraTeam and they have not already been mapped 11 2 4 Configuring the Standard Field Mapping Now that the projects user and releases have been mapped correctly we need to configure the standard incident fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the RedmineDataSync plug in entry RedmineDataSync Project Data Mapping Redmine Demo Project Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the RedmineDataSync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Redmine Demo Project External Key spira redmine demo project Active Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that
11. that will be used to store the environment description within SpiraTeam Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Sample OnTime Project Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the OnTimeDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name ReplicationProcedures External Key ReplicationProcedures All you need to do on this screen is enter the word ReplicationProcedures in the External Key textbox and the data sync plug in will know that this custom property is mapped to the built in Replication Procedures field in OnTime Note that there is no space between the words Replication and Procedures Once you have updated the various mapping sections you are now ready to start the service 12 3 Enabling the Data Synchronization 12 3 1 Starting the Service When SpiraTeam is installed a Windows Service SpiraTeam Data Sync Service is installed along with the web application However to avoid wasting system resources this service is initially set to run manually To ensure continued synchronization of SpiraTeam with OnTime we recommend starting the service
12. 44 Once you have found the matching Area by name the numeric value stored in the ID column the one on the left is the value that needs to get added as the External Key inside SpiraTeam b TFS Custom Fields If the custom field in TFS is a list field first you need to go to Administration gt Edit Custom Lists in SpiralTeam and create a new custom list that contains all the different values that are being used in TFS Then for both list fields and value fields you need to go to Administration gt Edit Custom Properties and add a new custom property onto the Incident artifact type with the name of the appropriate TFS field e g Triage Rank etc and if a list field link it to the custom list you created in the previous step The custom property will now be available for data mapping Now back in the data synchronization data mapping page click on the hyperlink under Incident Custom Properties that corresponds to the custom property to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping TFS Test Project 1 Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the MsTisDataSync extemal key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Trage External Key Microsoft VS5T5 Common Triage Cu
13. Duplicate New Not Reproducible Open Reopen Wer kd Resolved The table lists each of the incident statuses available in SpiraTeam and provides you with the ability to enter the matching FogBugz case status ID for each one You can map multiple SpiraTeam fields to the same FogBugz fields e g New Open Assigned and Reopen in SpiraTeam are all equivalent to Active in FogBugz in which case only one of the four values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from FogBugz gt SpiraTeam We recommend that you always point the New Open Assigned and Reopen statuses inside SpiraT eam to point to the ID for Assigned inside FogBugz and make Assigned in Spiraleam the Primary status of the four This is recommended so that as new incidents in SpiraTeam get synched over to FogBugz they will get switched to the Active status in FogBugz which will then be synched back to Assigned in SpiraTeam That way you ll be able to see at a glance which incidents have been synched with FogBugz and those that haven t You also might want to consider changing the statuses in SpiraTeam to match the 16 discrete statuses in FogBugz to make things easier for your users In which case you ll need to create the new statuses and configure the workflow as described in the Spiraleam Administration Guide The status IDs in FogBugz are fixed and should be StatusID Status Name Pot Active
14. False then for data going into Mantis the User ID will be forced to that of the User ID in SpiraTeam Once you have entered the Mantis Login ID in click Update You should now repeat for the other users who will be active in both systems 7 2 3 Configuring the Release Mapping When the data synchronization service runs and it comes across a release in SpiraTeam or a Version in Mantis that it has not linked before it will create a corresponding entry in the other system When starting out a new project it is recommended that you let the MantisDataSync handle creation of the releases versions in either system and then edit the information once the link is made In cases where you are syncing up two existing projects in both systems it is advised that you link any existing releases that exist in both systems manually and then only create new releases in one system To link a release in SpiraTeam up to a version in Mantis please navigate to Planning gt Releases and click on the Release lteration in question Make sure you have the Overview tab visible and expand the Details section of the release iteration Release 3 0 0 1 New Release RL 000023 Name Overview Incidents Regs amp Tasks Test Cases Test Runs Attachments History L7 Details l o E i dl Start End Date Creation Date 6 5 2013 6 04 46 PM Resources Active Ys Non Working person days Iteration no Plan Effort 184
15. S8E eE SERVER database OnTinie puid USER pwa PASSWORDS gt lt add key SecurityToken value 66ACD352 16C0 4485 8498 8C461BE7CE44 gt lt add key WebServicesUser value 1 gt lt add key EnableDataCache value False gt lt appSettings gt You need to make sure that you fill out the ConnectionString that points to the Microsoft SQL Server database that OnTime is connecting to Also for the SecurityToken field you need to generate a new GUID and add it to the file This security token will be used by SpiraTeam when it connects to the OnTime API Once you have made the necessary changes save the file 12 1 2 Download the OnTime Plug In Go to the Inflectra website and open up the page that lists the various downloads available for SpiraTeam http www inflectra com Spiraleam Downloads aspx Listed on this page will be the OnTime11 Plug In for SpiraTeam Right click on this link and save the Zip compressed folder to the hard drive of the server where SpiraTeam is installed Open up the compressed folder and extract the OnTimeDataSync dll file and place it in the C Program Files SpiraTeam Bin folder it may be SpiraTest or SpiraPlan depending on which product you re running This folder should already contain the DataSyncService exe and DataSyncService exe config files that are the primary files used for managing the data synchronization between SpiraTeam and other systems If you do not have an on premise inst
16. That way you ll be able to see at a glance which incidents have been synched with OnTime and those that haven t Note The OnTime external key needs to exactly match the display name of the status inside OnTime If you change the name of a status in OnTime you ll need to update the value in the data mapping configuration as well b Incident Priority Click on the Priority hyperlink under Incident Standard Fields to bring up the Incident Priority mapping configuration screen Artifact Type Incident Field Name Priority Priori y 1 Critica 2 High 3 Medium d Low The table lists each of the incident priorities available in SpiraTeam and provides you with the ability to enter the matching OnTime priority name for each one You can map multiple SpiraTeam fields to the same OnTime fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from OnTime gt SpiraTeam Note The OnTime external key needs to exactly match the display name of the priority inside OnTime If you change the name of a priority in OnTime you ll need to update the value in the data mapping configuration as well c Incident Severity Click on the Severity hyperlink under Incident Standard Fields to bring up the Incident severity mapping configuration screen Artifact Type Incident Field Name Severity ix 2 High l High Impact 3 Medium es
17. available values are Priority Status normal aS normal ETA immediate Severity trivial text tweak The Mantis values are in the highlighted fields above Type these into the External Key field in Spiraleam Depending on your regional settings in both applications this field will likely be case sensitive You can map multiple SpiraTeam fields to the same Mantis fields just like described in Incident Type above 7 2 5 Configuring the Custom Property Mapping Now that the various SpiraTeam standard fields have been mapped correctly we need to configure the custom property mappings At the moment only custom fields in Mantis can be linked to custom fields in SpiraTeam From the View Edit Project Data Mapping screen you need to click on the name of the Incident Custom Property that you want to add data mapping information for Both field types in SpiraTeam can be linked up to any of the supported field types in Mantis Linking between the two systems is done in text values only that means that if you have a SpiraTeam custom list then the values that will be put into Mantis will be the strings of the list The same works for moving fields back from Mantis Rules for linking different field types up are as follows SpiraTeam List to Mantis Enum List or Multiselection For linking these types of fields together the available values must match For example if you have Windows as
18. 1 and can be used instead of the server based DataSyncService 11 1 2 Configuring the Service To configure the integration service please open up the DataSyncService exe config file located in C Program Files SpiralTeam Bin with a text editor such as Notepad Once open it should look like lt xml version 1 0 encoding utf 8 gt lt COnNLLigQUraLion gt lt configSections gt lt sectionGroup name applicationSettings type System Configuration ApplicationSettingsGroup System Version 2 0 0 0 Culture neutral PublicKeyToken b77a5c561934e089 gt lt section name Inflectra SpiraTest DataSyncService Properties Settings type System Configuration ClientSettingsSection System Version 2 0 0 0 Culture neutral PublickeyToken b77a5c561934e089 requirePermission false gt lt sectionGroup gt lt configSections gt lt applicationSettings gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt setting name PollingInterval serializeAs String gt lt value gt 600000 lt value gt lt setting gt lt setting name WebServiceUrl serializeAs String gt lt value gt http localhost SpiraTeam lt value gt lt setting gt lt setting name Login serializeAs String gt lt value gt Yre dbl6ggs lt value gt lt setting gt lt setting name Password serializeAs String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name EventLogSource serializeAs String g
19. As Local System Local Systern Local System Local System Local System Local Service beat Spa Local System Local Systern Local Service Local Systern Local System Local Systerh Local Service Local Systert lasal C bam Siy TCP IP NetBIOS Helper Siy Telephony a Talaa Enables support For NetBIOS over TCP IP N Provides Telephany API TAPI support For p an beh been Caskhias amp emma i a be snme extended Standard Click on the SpiraTeam Data Sync Service entry and click on the link to start the service Then right click the service entry and choose the option to set the startup type to Automatic This will ensure that synchronization continues between SpiraTeam and FogBugz after a reboot of the server 6 3 2 Using SpiraTeam with FogBugz Now that the integration service has been configured and the service started initially any incidents created in SpiraTeam for the specified projects will be imported into FogBugz and any existing cases in FogBugz will get loaded into SpiraTeam At this point we recommend opening the Windows Event Viewer and choosing the Application Log In this log any error messages raised by the SpiraTeam Data Sync Service will be displayed If you see any error messages at this point we recommend immediately stopping the SpiraTeam service and checking the various mapping entries If you cannot see any cases with the mapping information we recommend sending a copy of t
20. Closed Closed Duplicate Duplicate New Submitted Not Reproducible D A Ajj lt iT i Open Opened Reopen T on iT i l ll ll lt B Resolved Resolved The table lists each of the incident statuses available in SpiraTeam and provides you with the ability to enter the matching ClearQuest issue status name for each one You can map multiple SpiraTeam fields to the same ClearQuest fields e g Open and Reopen in SpiraTeam are both equivalent to Opened in ClearQuest in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from ClearQuest gt SpiraTeam b Incident Priority Click on the Priority hyperlink under Incident Standard Fields to bring up the Incident Priority mapping configuration screen Edit standard Field Data Mapping Sample Application Two Change Project lt lt Back to Project Mappings To configure the data mappings for this fleld please fill in the external key values for the ClearQuestDataSync plug in next to each opiraleam value Critical High Medium Low The table lists each of the incident priorities available in SpiraTeam and provides you with the ability to enter the matching ClearQuest priority name for each one You can map multiple SpiraTeam fields to the same ClearQuest fields in which case only one of the two values can be listed as Primary Yes as that s
21. Data Synchronization 11 3 1 Starting the Service When SpiraTeam is installed a Windows Service SpiraTeam Data Sync Service is installed along with the web application However to avoid wasting system resources this service is initially set to run manually To ensure continued synchronization of SpiraTeam with Redmine we recommend starting the service and setting its startup type to Automatic To make these changes open up the Windows Control Panel click on the Administrative Tools link and then choose the Services option This will bring up the Windows Service control panel nu Services Fle Acton View Help Behe e y Services Local ie Services Local SpiraTeam Data Sync Service Name Description Status Startup Type Log On As Sy Secunty Accounts Manager Stores security information For local user ace Started Automatic Local System Start the service 8B Security Center Monitors system security settings and config Automatic Local Systern By Server Supports File print and named pipe sharing Started Automatic Local System Description By Shel Hardware Detection Provides notifications for AutoPlay hardware Started Automatic Local System banaane Marea r kanaa A i Sa Simple Mail Transfer Protocol SMTP Transports electronic mail across the network Manual Local System systems Sey Smart Card l Manages access to smart cards read by this Mariual Local Service Spira Team Data Syne Service Manages the data
22. Enables support For NetBIOS over TCP IP N Provides Telephany API TAPI support For p an beh been Caskhias amp emma i a be snme extended Standard Click on the SpiraTeam Data Sync Service entry and click on the link to start the service Then right click the service entry and choose the option to set the startup type to Automatic Delayed or Automatic This will ensure that synchronization continues between SpiraTeam and Mantis after a reboot of the server 7 3 2 Using SpiraTeam with Mantis Now that the integration service has been configured and the service started initially any incidents created in SpiraTeam for the specified projects will be imported into Mantis and any existing issues in Mantis will get loaded into SpiraTeam After the first sync we recommend opening the Windows Event Viewer and viewing the Application Log Any errors unable to connect messages invalid required field mappings and warnings incomplete field mappings will be displayed If on Server 2008 Vista or later you can filter by the Application name MantisDataSync If you see any error messages or warning messages that you want to correct before continuing at this point we recommend immediately stopping the SpiraTeam service and checking the various mapping entries If you cannot see any issues with the mapping information we recommend sending a copy of the event log message s to Inflectra customer services S
23. FogBugz we recommend starting the service and setting its startup type to Automatic To make these changes open up the Windows Control Panel click on the Administrative Tools link and then choose the Services option This will bring up the Windows Service control panel niu Services Fle Action View Help Beoe AM gt Gy Services Local i Services Local SpiraTeam Data Sync Service Start the service Description Manages the data synchronization between SpiraTeam and other external systems Name Sy Secunty Accounts Manager By Security Center egy Server Sa Shell Hardware Detection Sia Simple Mail Transfer Protocol SMTP By Smart Card th SpiraTeam Data Syne Service By SQLAgentsSPIRA Sy SOLSERVERAGENT By SSOP Discovery Service Siy System Event Notification By System Restore Service Sf Task Scheduler Description Stores security information For local user acc Monitors system security settings and config Supports File print and named pipe sharing Provides notifications For AutoPlay hardware Transports etachronic mail across the network Manages access to smart cards read by this Enables cescovery of UPnP devices on your h Tracks system events such as Windows laga Performs system restore functions To stop Enables a user to configure and schedule au Status Started Started Started Startup Type Aornatic Automatic Automatic Akomatic Manual Maral Lag On
24. Help ae Fle Archon E By Services Local i Services Local SpiraTeam Data Sync Service Start the service Description Manages the data synchromization between SpiraTeam and other external systems extended Standard Click on the SpiraTeam Data Sync Service entry and click on the link to start the service Then right click the service entry and choose the option to set the startup type to Automatic This will ensure that Name 4 Secunty Accourts Manager Sy Security Center Server By Sheil Hardware Detection Sia Simple Mail Transfer Protocol SMTP By Smart Card Spira Team Dats Syne Service SH SOLAgentsSPIRA SY SQLSERVER AGENT 8 SSDP Discovery Service Sy System Event Notification Sy System Restore Service Sf Task Scheduler My TCP IP NetBIOS Helper Sia Telephony Bs Talna Description Stores security information For local user acc Monitors system security settings and config Supports File print and named pipe sharing Provides notifications For AutoPlay hardware Transports electronic mail across the network Manages access to smart cards read by this Manages the data synchronization between Enables cescovery of UPn devices on your R Tracks system everits such as Windows lago Performs system restore Functions To stop Enables a user to configure and schedule au Enables support For NetBIOS over TCP IP N Provides Telephany API TAPI support For p
25. Make sure that when you enter this URL on a browser on the server itself the application login page appears gt Avvalid login name and password to your instance of SpiraTeam This user needs to be a member of the project s that will be synchronized with FogBugz and needs to have at least Incident create modify view permissions and Release create modify view permissions in these projects Once you have made these changes save the file and proceed to the next stage 6 1 3 Configuring the Plug In The next step is to configure the plug in within SpiraTeam so that the system knows how to access the FogBugz server To start the configuration please open up SpiraTeam in a web browser log in using a valid account that has System Administration level privileges and click on the System gt Data Synchronization administration option from the left hand navigation Data Synchronization Refresh SpiraTeam is able to communicate with a variety of external systems and applications using its background data synchronization service and library of available plug ins This page allows you to view add and modify the list of plug ins make changes to their configuration and verify the status of the most recent synchronization In addition you can force a particular plug in to perform a complete data synchronization by resetting its date of last sync FogBugzDataSync gt View Project Mappings 6 1 2009 2 37 29 PM Success gt Force Re Sync Edit
26. Medium Impact 4 Low The table lists each of the incident severities available in SpiraTeam and provides you with the ability to enter the matching OnTime severity name for each one You can map multiple SpiraTeam fields to the same OnTime fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from OnTime gt SpiraTeam Note The OnTime external key needs to exactly match the display name of the severity inside OnTime If you change the name of a severity in OnTime you ll need to update the value in the data mapping configuration as well 10 2 5 Configuring the Custom Property Mapping Now that the various SpiraTeam standard fields have been mapped correctly we need to configure the custom property mappings This is used for both custom properties in SpiraTeam that map to custom fields in OnTime and also for custom properties in SpiraTeam that are used to map to standard fields in OnTime currently only Replication Procedures that don t exist in SpiraTeam From the View Edit Project Data Mapping screen you need to click on the name of the Incident Custom Property that you want to add data mapping information for We will consider the three different types of mapping that you might want to enter Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that
27. Name of the TFS field as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to this specific field in TFS To see a list of fields and their reference names you can run the following SQL query against your TFS database SELECT Name ReferenceName FROM Fields ORDER BY Name We have included a list of fields in the Agile process template in section 5 5 of this guide as a helpful reference Next for each of the Property Values in the table in the lower half of the page you need to enter the name of the field values as they appear in TFS as the External Key 5 2 8 Configuring the Standard Requirement Field Mapping 2012 Plugin Only Now that the projects user releases incident and task fields have been mapped correctly we need to configure the standard requirement fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the MsTfsDataSync plug in entry Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Requirement Importance Area Status Risk Test Case Prionty Incident FPrionty Area Severity Stack Rank Status Release Task From this screen you need to click on Importance and Status in turn to configure their values a Requirement Status
28. Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the FogbugzDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Version External Key Version ee I z Ti menm All you need to do on this screen is enter the word Version in the External Key textbox and the data sync plug in will know that this custom property is mapped to the built in Version field in FogBugz c FogBugz s Area Field You first need to create an incident custom property in SpiraTeam of type LIST that will be used to store the list of project areas within SpiraTeam You will need to create a new custom list to store the different possible values of area and then use that list when creating the new custom property Then back on the Data Mapping page click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Library Information System Change Project lt lt Back to Project Mappint To configure the data mappings for this custom property please fill in the FogBugzDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property
29. SpiraTeam and provides you with the ability to enter the matching RTC work item status name for each one You can map multiple SpiraTeam fields to the same RTC fields e g Closed and Resolved in SpiraTeam are both equivalent to Complete in RTC in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from RTC gt SpiraTeam b Incident Type Click on the Type hyperlink under Incident Standard Fields to bring up the Incident type mapping configuration screen Edit Standard Field Data Mapping sample Application Two Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the RtcDataSyne plug in next to each spiraleam value a or aj Change Request o Enhancement a D Incident ai Issue aj Limitation Risk Training The table lists each of the incident types available in SpiraTeam and provides you with the ability to enter the matching RTC work item type name for each one You can map multiple SpiraTeam fields to the same RTC fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from RTC gt SpiraTeam 9 2 3 Configuring the Custom Property Mapping Now that the various SpiraTeam standard fields have been mapped correctly w
30. and setting its startup type to Automatic To make these changes open up the Windows Control Panel click on the Administrative Tools link and then choose the Services option This will bring up the Windows Service control panel i Services Fle Acton View Help Fone gem gt SpiraTeam Data Sync Service Name Deseription Status Startup Type Log On As 4 Sy Secunty Accounts Manager Stores security information For local user acc Started Autoratic Local System Start the service Security Center Monitors system security settings and config Automatic Local Systern By Server Supports File print and named pipe sharing Started Automatic Local System Description By Shel Hardware Detection Provides notifications For AutoPlay hardware Started Automatic Local System sanira the emt Vrt seni Sia Simple Mail Transfer Protocol SMTP Transports electronic mail across the network Manual Local System wn se SSE SE I amp Smart Card Manages access to smart cards read by this Mariual Local Service te SpirsTeam Data Syne Service Manages the data synchronization between Local System SH SOLAgent SPIRA Local System SHY SQLSERVERAGENT Local Systern amp 550P Descovery Service Enables cescovery of UPnP devices on your R Local Service Sy System Event Notification Tracks system everits such as Windows loga Local Systern By System Restore Service Performs system restore Functions To stop Local System Sf Task Scheduler Enabl
31. below Note Once you have successfully configured the project when creating a new project you should choose the option to Create Project from Existing Project rather than Use Default Template so that all the project mappings get copied across to the new project if you are going to want to Sync the new project up to Mantis 7 2 2 Configuring the User Mapping To configure the mapping of users in the two systems you need to go to Administration gt Users gt View Edit Users which will bring up the list of users in the system Then click on the Edit button for a particular user that will be editing issues in Mantis Add Edit User Fox Michaels Please review the information listed below and make any changes if necessary Once you have finished click Update Insert to confirm them First Name Middle Initial Last Name User Name Email Address System Administrator Active User Ye F Mantis Data Sync ID LDAP Managed User E Change Password You will notice that below the Active flag for the user is a list of all the configured data synchronization plug ins In the text box next to the MantisDataSync ID you need to enter the Login ID of this user in Mantis If you have the Automap Users checkbox enabled in the MantisDataSync plugin then if no link is created the system will scan for a matching Login ID from both systems and use a match If you then do not have Custom3 set to
32. built in Environment field in JIRA f JIRA s Security Level Field If your instance of JIRA requires that all new issues are submitted with a Security Level then you will need to fill out this section You first need to create an incident custom property in SpiraTeam of type LIST that contains the various security levels that exist inside JIRA Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen First you need to enter the word SecurityLevel as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Security Level field in JIRA Next for each of the Property Values in the table in the lower half of the page you need to enter the JIRA ID of the various Security Levels that are configured in JIRA The external ID can be found by looking at the URL inside JIRA which choosing to View Edit the security level name description JIRA s Issue Key Field It can be convenient to create a SpiraTeam custom property to store the JIRA Issue Key the ID used to identify an issue in JIRA This allows you to display a list of incients in SpiraTest and see the corresponding JIRA ID in the same list You first need to create an incident custom property in SpiraTeam of type TEXT that will be used to store the JIRA issue key within SpiraTeam Then
33. cases managed by SpiraTest Spiraleam and the incidents managed on behalf of SpiraTest SpiraTeam inside ClearQuest 9 Using SpiraTeam with IBM RTC This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with the IBM Rational Team Concert hereafter referred to as RTC work item tracking system The built in integration service allows the quality assurance team to manage their requirements and test cases in SpiraTeam execute test runs in SpiraTest and then have the new incidents generated during the run be automatically loaded into RTC Once the incidents are loaded into RTC as work items the development team can then manage the lifecycle of these work items in RTC and have the status changes in RTC be reflected back in SpiraTeam In addition any issues logged directly into RTC will get imported into SpiraTeam so that they can be linked to test cases and requirements 9 1 Configuring the Integration Service This section outlines how to configure the integration service to export incidents into RTC and pick up subsequent status changes in RTC and have them be updated in SpiraTeam It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam v3 0 or higher and a working installation of RTC 2 0 or higher If you have an earlier version of SpiraTeam you will need to upgrade to at least v3 0 before trying to integrate with RTC The steps that nee
34. currently selected project RedmineDataSync Project Data Mapping Redmine Demo Project Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the RedmineDataSync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Redmine Demo Project External Key spira redmine demo project Active Yes Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Artifact Standard Fields Requirement Importance Status Test Case Priority Incident Priority Severity Status Type Release Task Priority Status If the project name does not match the name of the project you want to configure the data mapping for click on the Change Project hyperlink to change the current project To enable this project for data synchronization with Redmine you need to enter gt External Key This should be set to the name of the equivalent project in Redmine gt Active Flag Set this to Yes so that SpiraTeam knows that you want to synchronize data for this project Once the project has been completed setting the value to No will stop data synchronization
35. data mapping with the JiraDataSync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name JIRA DEMO Project Active Yes v Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Requirement Importance Status Test Case Priority Incident Priority Custom Date Severity Free Text Field Status Multi Select Field Type Single Select List Custom User Components Environment Release Task Priority Status From this screen you need to click on Priority Severity Status and Type in turn to configure the incident field mappings If you re using the option to have JIRA also synchronize some issue types as requirements then you ll need to also configure the Requirement Importance and Status fields a Incident Type Click on the Type hyperlink under Incident Standard Fields to bring up the Incident type mapping configuration screen Edit Standard Field Data Mapping JIRA DEMO Project Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the JiraDataSync plug in next to each Spiraleam value th Bug Yes Change Reques
36. four different types of mapping that you might want to enter JiraDataSync Project Data Mapping JIRA DEMO Project Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the JiraDataSync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name JIRA DEMO Project External Key DEMO Active Yes v Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Requirement Importance Status Test Case Priority Incident Priority Custom Date Severity Free Text Field Status Multi Select Field Type Single Select List Custom User Components Environment Release Task Priority Status a Scalar Custom Properties This refers to custom properties that have a simple user entered value and don t need to have their specific options mapped between SpiraTeam and JIRA All of the custom property types except List and Multi List fall into this category e g Text Date User Boolean Decimal Integer etc Click on the hyperlink of the scalar custom property under Incident Requirement Custom Properties to bring up the custom property mapping configuration screen For scalar c
37. full Reference Name of the TFS field as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to this specific field in TFS To see a list of fields and their reference names you can run the following SQL query against your TFS database SELECT Name ReferenceName FROM Fields ORDER BY Name We have included a list of fields in the Agile process template in section 5 5 of this guide as a helpful reference Next for each of the Property Values in the table in the lower half of the page you need to enter the name of the field values as they appear in TFS as the External Key Once you have updated the various mapping sections you are now ready to start the service 5 3 Enabling the Data Synchronization 5 3 1 Starting the Service When SpiraTeam is installed a Windows Service SpiraTeam Data Sync Service is installed along with the web application However to avoid wasting system resources this service is initially set to run manually To ensure continued synchronization of SpiraTeam with TFS we recommend starting the service and setting its startup type to Automatic To make these changes open up the Windows Control Panel click on the Administrative Tools link and then choose the Services option This will bring up the Windows Service control panel niu Services Fle Action View Help w soe Am gt Sey Services Local i Services Local
38. get imported into SpiraTeam as either new incidents or new requirements depending on their type so that they can be used as part of the planning and testing lifecycle 2 1 Configuring the Integration Service This section outlines how to configure the integration service to export incidents into JIRA import new issues from JIRA and pick up subsequent status changes in JIRA and have them update SpiraTeam It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam and a working installation of JIRA The following versions of SpiraTeam and JIRA are supported gt The JIRA 5 x plugin supports JIRA 5 0 or later and SpiraTeam v4 0 or later gt The JIRA 4 x plugin supports JIRA 4 0 or later and SpiraTeam v3 0 or later see section 3 gt The JIRA 3 x plugin supports JIRA 3 0 or later and SpiraTeam v2 3 or later See section 3 If you have an earlier version of SpiraTeam you will need to upgrade to at least v2 3 before trying to integrate with JIRA The steps that need to be performed to configure integration with JIRA are as follows Download the latest JIRA Data Sync 5 x plug in for SpiraTeam from our website Vv Setup the plug in in SpiraTeam to point to the correct instance of JIRA gt Configure the data field mappings between SpiraTeam and JIRA gt Start the service and verify data transfer 2 1 1 Download the JIRA Plug in Go to the Inflectra website and open up the page that lists the various
39. gt lt setting name PollingInterval serializeAs String gt lt value gt 600000 lt value gt lt setting gt lt setting name WebServiceUrl serializeAs String gt lt value gt http localhost SpiraTeam lt value gt lt setting gt lt setting name Login serializeAs String gt lt value gt Yre dbl6ggs lt value gt lt setting gt lt setting name Password serializeAs String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name EventLogSource serializeAs String gt lt value gt SpiraTeam Data Sync Service lt value gt lt setting gt lt setting name TraceLogging serializeAs String gt lt value gt False lt value gt lt setting gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt applicationSettings gt lt contiquration gt The sections that need to be verified and possibly changed are marked in yellow above You need to check the following information gt The polling interval allows you to specify how frequently the data synchronization service will ask Spiraleam and the external system for new data updates The value is specified in milliseconds and we recommend a value no smaller than 5 minutes i e 300 000ms The larger the number the longer it will take for data to be synchronized but the lower the network and server overhead gt The base URL to your instance SpiraTeam It is typically of the form http lt server name gt SpiraTeam
40. http localhost 8080 secure admin EditlssueTypeldefaultjspa id 1 b Incident Status Click on the Status hyperlink under Incident Standard Fields to bring up the Incident status mapping configuration screen Edit Standard Field Data Mapping JIRA DEMO Project Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the JiraDataSync plug in next to each Spiraleam value Assigned Clased Duplicate New Not Reproducible Open Reopen Resolved The table lists each of the incident statuses available in SpiraTeam and provides you with the ability to enter the matching JIRA issue status ID for each one You can map multiple SpiraTeam fields to the same JIRA fields e g New and Open in SpiraTeam are both equivalent to Open in JIRA in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from JIRA gt SpiraTeam We recommend that you always point the New and Open statuses inside SpiraTeam to point to the ID for Open inside JIRA and make Open in SpiraTeam the Primary status of the two This is recommended so that as new incidents in SpiraTeam get synched over to JIRA they will get switched to the Open status in JIRA which will then be synched back to Open in SpiraTeam That way you ll be able to see at a glance which incidents have been synche
41. in this field b TFS 2010 Plugin Please fill out the fields as follows gt gt gt Auto Map Users this is not used by this version of the plugin and can be ignored Custom 01 This is used to specify the Windows Active Directory Domain that the Windows user specified above is a member of If you are running TFS on a Windows workgroup just use the server name and make sure that the Windows user above is a user on that server itself Custom 02 This is used to specify if you want to synchronize Incidents Tasks or Both By default this field is blank meaning synchronize both types of artifact However if you enter in Incidents into this field it will tell the system to only synchronize incidents and if you enter Tasks it will tell the system to only synchronize tasks Custom 03 If you would like the system to display the SpiraTeam artifact ID e g IN5 for incidents or TK36 for tasks in a custom field inside TFS you should just enter the name of the appropriate TFS field from your process template e g Soira IncidentId and then when the incident or task is added to TFS the corresponding Spiraleam ID will be added to that field of the work item Custom 04 Depending on your TFS process template the data synchronization plugin may not be allowed to set the detector of the incident inside TFS If you would like the system to display the detector of the incident as recorded in SpiraTeam in a custom field
42. in this project Artifact Incident Release Notes Operating System Task a FogBugz s Computer Field You first need to create an incident custom property in SpiraTeam of type TEXT that will be used to store the Computer description within SpiraTeam Then click on the hyperlink of this new text custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the FoqBugzDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Computer ii All you need to do on this screen is enter the word Computer in the External Key textbox and the data sync plug in will know that this custom property is mapped to the built in Computer field in FogBugz b FogBugz s Version Field You first need to create an incident custom property in SpiraTeam of type TEXT that will be used to store the Version description within SpiraTeam Then click on the hyperlink of this new text custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Library Information System Change
43. in your installation or not you will see either an empty screen or a list of sample data synchronization plug ins If you already see an entry for RedmineDataSync you should click on its Edit link If you don t see such an entry in the list please click on the Add button instead In either case you will be taken to the following screen where you can enter or modify the Redmine Data Synchronization plug in Edit Plug In RedmineDataSync lt lt Back to Data Synchronization Home Please enter edit the following information for the plug in The exact information that needs to be entered is specific to each plug in and you should refer to the documentation for the plug in when entering changing it Name RedmineDataSync Description synchronizes incidents in Spiraleam with issues in Redmine Connection htip demo redmine org Info Login inflectratest Password Siibkeee Time Offset C Auto Map Users Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 You need to fill out the following fields for the Redmine Plug in to operate correctly gt Name this needs to be set to RedmineDataSync This needs to match the name of the plug in DLL assembly that was copied into the C Program Files SpiraTeam Bin folder minus the dll file extension If you renamed the RedmineDataSync dll file for any reason then you need to change the name here to match gt Description this should be set to a descripti
44. is open and ready for the assignee to start work on it In Progress Active jira Edit This issue is being actively worked on at the moment by the assignee i Reopened Active e jira Edit This issue was once resolved but the resolution was deemed incorrect From here issues are either marked assigned or resolved ip Resolved Active jira Edit A resolution has been taken and it is awaiting verification by reporter From here issues are either reopened or are closed Closed Active jira Edit The issue is considered finished the resolution is correct Issues which are closed can be reopened f Requirement Importance Optional Click on the Importance hyperlink under Requirement Standard Fields to bring up the Requirement Importance mapping configuration screen Edit Standard Field Data Mapping JIRA DEMO Project Change Project lt lt Back to Project Mappi To configure the data mappings for this field please fill in the external key values for the JiraDataSync plug in next to each Spiraleam value Field Value 1 Critical 2 High 3 Medium 4 Low The table lists each of the requirement importances available in SpiraTeam and provides you with the ability to enter the matching JIRA priority ID for each one You can map multiple SpiraTeam fields to the same JIRA fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronizati
45. key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Hardware External Key Hardware First you need to enter the word Hardware as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Hardware field in Bugzilla Next for each of the Property Values in the table in the lower half of the page you need to enter the Bugzilla name of the various Hardware platforms that are configured in Bugzilla d Bugzilla s Resolution Field Optional When incidents in SpiraTeam are updated with changes made in Bugzilla the value of the Bugzilla resolution field FIXED INVALID WONTFIX LATER REMIND DUPLICATE WORKSFORME MOVED DEPLOY is used to populate the Resolution Comments text box within SpiraTeam However the Resolution Comments field in SpiraTeam cannot be displayed in the incident list page as it s a long text field so if you would like to be able to see the list of Bugzilla Resolution codes displayed in a list it is necessary to add a TEXT custom property to Incidents that can be used to store this returned value and then be filtered in the list The rest of this section describes how to map this text custom property so that it picks up the Resolution field values from Bugzilla To configure the mapping click on the hype
46. mapping for click on the Change Project hyperlink to change the current project To enable this project for data synchronization with FogBugz you need to enter gt External Key This should be set to the ID of the project in FogBugz This can be found by navigating to Settings gt Projects in FogBugz Edit Delete Project Client Department Primary Contact Report Description Ey Inbox Internal Adam Inbox for FogBugz Autosort Ey al Sample Project Internal Adam Ey Create New Project Then hover the mouse over the project name The project ID will be displayed in the URL line as ixProject X where X is the numeric ID of the project gt Active Flag Set this to Yes so that SpiraTeam knows that you want to synchronize data for this project Once the project has been completed setting the value to No will stop data synchronization reducing network utilization Click Update to confirm these settings Once you have enabled the project for data synchronization you can now enter the other data mapping values outlined below Note Once you have successfully configured the project when creating a new project you should choose the option to Create Project from Existing Project rather than Use Default Template so that all the project mappings get copied across to the new project 6 2 2 Configuring the User Mapping To configure the mapping of users in the two systems you need to go to Admi
47. of merchantability fitness for a particular purpose or non infringement This publication could include technical inaccuracies or typographical errors Changes are periodically added to the information contained herein these changes will be incorporated in new editions of the publication Inflectra Corporation may make improvements and or changes in the product s and or program s and or service s described in this publication at any time The sections in this guide that discuss internet web security are provided as suggestions and guidelines Internet security is constantly evolving field and our suggestions are no substitute for an up to date understanding of the vulnerabilities inherent in deploying internet or web applications and Inflectra cannot be held liable for any losses due to breaches of security compromise of data or other cyber attacks that may result from following our recommendations SpiraTest SpiraPlan SpiraTeam and Inflectra are registered trademarks of Inflectra Corporation in the United States of America and other countries Microsoft Windows Explorer and Microsoft Project are registered trademarks of Microsoft Corporation All other trademarks and product names are property of their respective holders Please send comments and questions to Technical Publications Inflectra Corporation 8121 Georgia Ave Suite 504 Silver Spring MD 20910 4957 U S A support inflectra com
48. of the project identifiers for the projects that need to be synchronized gt The mapping of users in the system gt The mapping of releases equivalent to FogBugz releases fix fors in the system gt The mapping of the various standard fields in the system gt The mapping of the various custom properties in the system Each of these is explained in turn below 6 2 1 Configuring the Project Mapping From the data synchronization administration page you need to click on the View Project Mappings hyperlink next to the FogBugz plug in name This will take you to the data mapping home page for the currently selected project View Edit Project Data Mapping Library Information System Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the FogBugzData Sync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Library Information System Artifact Field Mapping Please click on each of the links below to configure the fleld level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority Severity Status Type Release te Operating System Task Priority Status If the project name does not match the name of the project you want to configure the data
49. of the requirement importance values available in SpiraTeam and provides you with the ability to enter the matching TFS work item priority value for each one 5 2 9 Configuring the Requirement Custom Property Mapping 2012 Plugin Only Now that the various SpiraTeam standard requirement fields have been mapped correctly we need to configure the custom property mappings This is used for both custom properties in SpiraTeam that map to custom fields in TFS and also for custom properties in SpiraTeam that are used to map to standard fields in TFS e g Area that don t exist in SpiraTeam From the View Edit Project Data Mapping screen you need to click on the name of the Requirement Custom Property that you want to add data mapping information for Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Requirement Importance Status Test Case Prionty Incident Pnonty Severity Status Release Task Prionty Status a TFS s Area Field First you need to go to Administration gt Edit Custom Lists and create a new custom list that contains all the different Areas that are being used in TFS Then you need to go to Administration gt Edit Custom Properties and add a new ist custom property onto the Requirement artifact type called Area and link it to the Area custom list you created in the
50. please make sure you download the correct version gt Setup the plug in in SpiraTeam to point to the correct instance of Bugzilla gt Configure the data field mappings between SpiraTeam and Bugzilla gt Start the service and verify data transfer 4 1 1 Download the Bugzilla Plug In Go to the Inflectra website and open up the page that lists the various downloads available for SpiraTeam http www intlectra com Spiraleam Downloads aspx Listed on this page will be the Bugzilla Plug In for Spiraleam Right click on this link and save the Zip compressed folder to the hard drive of the server where SpiraTeam is installed Note There are separate plug ins for Bugzilla 3 x and Bugzilla 4 x so please make sure you download the correct version Open up the compressed folder and extract the BugzillaDataSync dll file and place it in the C Program Files SpiraTeam Bin folder it may be SpiraTest or SpiraPlan depending on which product you re running This folder should already contain the DataSyncService exe and DataSyncService exe config files that are the primary files used for managing the data synchronization between Spiraleam and other systems If you do not have an on premise installation of SpiraTeam but instead are using a hosted subscription provided by Inflectra or a third party company you will not have access to the DataSyncService background service In such situations you should use the Desktop DataSync application instead Thi
51. previous step This will now be available for mapping Now back in the data mapping page click on the Area hyperlink under Requirement Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping TFS Test Project 1 Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the MsTisDataSync extemal key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Area Custom Value Mapping Administration Customization Management Reporting First you need to enter the word Area as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Area field in TFS Next for each of the Property Values in the table in the lower half of the page you need to enter the ID of the various Areas that are configured in TFS The TFS Area ID is not visible in the TFS user interface but can instead be located by opening up the SQL Server that it s installed on opening the TfsWorkltem Tracking database in TFS 2010 and later it will named after your project collection instead and locating the TreeNodes table TypelD 44 44 44 Once you have found the matching Area by name the numeric value stored in
52. project for data mapping with the JiraDataSync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Library Information System Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority Environment i Motes Component Operating System Release Motes Operating System Task a Text Custom Properties Click on the hyperlink of the text custom property under Incident Custom Properties to bring up the custom property mapping configuration screen For text custom properties there will be no values listed in the lower half of the screen Edit Custom Property Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Notes External Key 49979 Custom Value Mapping You need to lookup the ID of the custom field in JIRA that matches this custom property in SpiraTeam Once you have entered the id of the custom field cl
53. reducing network utilization Click Update to confirm these settings Once you have enabled the project for data synchronization you can now enter the other data mapping values outlined below Note Once you have successfully configured the project when creating a new project you should choose the option to Create Project from Existing Project rather than Use Default Template so that all the project mappings get copied across to the new project 11 2 2 Configuring the User Mapping To configure the mapping of users in the two systems you need to go to Administration gt Users gt View Edit Users which will bring up the list of users in the system Then click on the Edit button for a particular user that will be editing issues in Redmine Add Edit User Rory Jones Please review the information listed below and make any changes if necessary Once you have finished click Update Insert to confirm them First Name Middle Initial Last Name User Name Department Email Address Email Enabled System Administrator Active Rory ones roryjones Software Engineering roryjonesi mycompany com No YF No Y Yes Y Locked Out o F RSS Token L Enable RSS Feeds Update Cancel Ls You will notice that in the special Data Mapping tab for the user is a list of all the configured data synchronization plug ins In the text box next to the Redmine Data Sync plug i
54. sample data synchronization plug ins If you already see an entry for RtcDataSync you should click on its Edit link If you don t see such an entry in the list please click on the Add button instead In either case you will be taken to the following screen where you can enter or modify the RTC Data Synchronization plug in Edit Plug In RtcDataSyne lt lt Back ta Data Synchronization Home Please enterfedit the following information for the plug in The exact information that needs to be entered is specific to each plug in and you should refer to the documentation for the plug in when entering changing it Hame Description Connection Info Login Password Time Offset Custom 01 Custom O2 Custom z Custom Custom 05 You need to fill out the following fields for the RTC Plug in to operate correctly gt Name this needs to be set to RtcDataSync This needs to match the name of the plug in DLL assembly that was copied into the C Program Files SpiraTeam Bin folder minus the dll file extension If you renamed the RtcDataSync dll file for any reason then you need to change the name here to match gt Description this should be set to a description of the plug in This is an optional field that is used for documentation purposes and is not actually used by the system gt Connection Info this should be the base URL for connecting to your instance of RTC for example http
55. see at a glance which incidents have been synched with OnTime and those that haven t Note The OnTime external key needs to exactly match the display name of the status inside OnTime If you change the name of a status in OnTime you ll need to update the value in the data mapping configuration as well b Incident Priority Click on the Priority hyperlink under Incident Standard Fields to bring up the Incident Priority mapping configuration screen 1 Critical 2 High 3 Medium 4 Low The table lists each of the incident priorities available in SpiraTeam and provides you with the ability to enter the matching OnTime priority name for each one You can map multiple SpiraTeam fields to the same OnTime fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from OnTime gt SpiraTeam Note The OnTime external key needs to exactly match the display name of the priority inside OnTime If you change the name of a priority in OnTime you ll need to update the value in the data mapping configuration as well c Incident Severity Click on the Severity hyperlink under Incident Standard Fields to bring up the Incident severity mapping configuration screen 1 Critical 2 High E High Impact 3 Medium res Medium Impact 4 Low e Low Impact The table lists each of the incident severities available in Spir
56. status If the project name does not match the name of the project you want to configure the data mapping for click on the Change Project hyperlink to change the current project To enable this project for data synchronization with RTC you need to enter gt External Key This should be set to the display name of the project in RTC that will be mapped to the specific SpiraTeam project gt Active Flag Set this to Yes so that SpiraTeam knows that you want to synchronize data for this project Once the project has been completed setting the value to No will stop data synchronization reducing network utilization Click Update to confirm these settings Once you have enabled the project for data synchronization you can now enter the other data mapping values outlined below Note Once you have successfully configured the project when creating a new project you should choose the option to Create Project from Existing Project rather than Use Default Template so that all the project mappings get copied across to the new project 9 2 2 Configuring the Standard Field Mapping Now that the projects user and releases have been mapped correctly we need to configure the standard incident fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the RtcDataSync plug in entry RtcDataSyne Project Data Mapping Sample Application
57. statuses priorities severities and custom property values used in the two applications to be related to each other This is important as without a correct mapping there is no way for the integration service to know that a New item in SpiraTeam is equivalent to a Submitted item in ClearQuest for example The following mapping information needs to be setup in Spiraleam gt The mapping of the project identifiers for the projects that need to be synchronized gt The mapping of users in the system The mapping of the various standard fields in the system gt The mapping of the various custom properties in the system Each of these is explained in turn below 8 2 1 Configuring the Project Mapping From the data synchronization administration page you need to click on the View Project Mappings hyperlink next to the ClearQuest plug in name This will take you to the data mapping home page for the currently selected project ClearQuestDatasync Project Data Mapping Sample Application Two Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the ClearQuestDataSyne plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization ta operate Project Name Sample Application Two External Key SAKAPL Update Artifact Fi
58. stop Status Started Started Started Startup Type Aornatic Automatic Automatic Akomatic Manual Maral Lag On As Local System Local Systern Local System Local System Local System Local Service beat Spa Local System Local Systern Local Service Local Systern Local System Sy Task Scheduler Sy TCP IP NetBIOS Helper Siy Telephony ae Talas Enables a user to configure and schedule au Enables support For NetBIOS over TCP IP N Provides Telephany API TAPI support For p as hah bhe Cashing amp emonnk Local Systerh Local Service Local Systert maad ase lasal C bam extended Standard Click on the SpiraTeam Data Sync Service entry and click on the link to start the service Then right click the service entry and choose the option to set the startup type to Automatic This will ensure that synchronization continues between SpiraTeam and RTC after a reboot of the server 9 3 2 Using SpiraTeam with ClearQuest Now that the integration service has been configured and the service started initially any incidents created in SpiraTeam for the specified projects will be imported into RTC and any existing work items in RTC will get loaded into SpiraTeam At this point we recommend opening the Windows Event Viewer and choosing the Application Log In this log any error messages raised by the SpiraTeam Data Sync Service will be displayed If you see any error messages at this point we rec
59. synchronizetion between Manual Local System By SOLAgentSsSPIRA Manual Local System Gy SOLSERVERAGENT Manual Local Systern y 550P Discovery Service Enables ciscovery of LIPD devices on your h Started Manual Local Service By System Event Notification Tracks system everits such as Windows lags Started Automatic Local Systern Sy System Restore Service Performs system restore Functions To stop Started Automatic Local System Shy Task Scheduler Enables a user to configure and schedule au Started Automatic Local System SRo TEPIP NetBIOS Helper Enables support For NetBIOS over TCP IP N Started Automatic Local Service Sy Telephony Provides Telephony API TAPI suppert f r p Started Marval Local Systert A ralnas ee ee eee Rive shin lasal c insam Click on the SpiraTeam Data Sync Service entry and click on the link to start the service Then right click the service entry and choose the option to set the startup type to Automatic This will ensure that synchronization continues between SpiraTeam and Redmine after a reboot of the server 11 3 2 Using SpiraTest with Redmine Now that the integration service has been configured and the service started initially any incidents created in SpiralTeam for the specified projects will be imported into Redmine At this point we recommend opening the Windows Event Viewer and choosing the Application Log In this log any error messages raised by the Data Synchronization service will
60. that are configured in JIRA Components Projects can be broken down into components e g Database User Interface Issues can then be categorised against different components Name Description Component Lead wL o i EE Project Default Pro v Add sg Component 1 The first component Project Default Delete Component 2 The second component Project Default Delete d JIRA s Resolution Field If you would like the values of the JIRA Resolution field to be synchronized back to SpiraTeam then you will need to fill out this section You first need to create an incident custom property in SpiraTeam of type LIST that contains the various resolution names that exist inside JIRA Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping JIRA DEMO Project Chan lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Resolution Custom Value Mapping Cannot Reproduce Fixed Won t Fix First you need to enter the word Resolution as the External Key of the custom property This tells the data sync plug in that the cus
61. that should be mapped to the built in SpiraTeam Incident Severity field which does not exist in JIRA This can be left empty for now and will be discussed below in section 3 2 gt Custom 02 05 these are not currently used by the plug in and should be left blank b JIRA 4 x Plugin Please fill out the fields as follows gt Auto Map Users This changes the way that the plugin maps users in SpiralTeam to those in JIRA gt Auto Map True With this setting all users in SpiraTeam need to have the same username as those in JIRA If this is the case then you do not need to perform the user mapping task outlined in section 3 2 2 This is a big time saver if you can guarantee that all usernames are the same in both systems gt Auto Map False With this setting users in SpiraTeam and JIRA are free to have different usernames because you specify the corresponding JIRA name for each user as outlined in section J22 gt Custom 01 This is used to specify a JIRA custom property that should be mapped to the built in SpiraTeam Incident Severity field which does not exist in JIRA This can be left empty for now and will be discussed below in section 3 2 gt Custom 02 This should be set to the word True if you want to have the new issues submitted to JIRA be submitted using a specified SecurityLevel If you re not using the security level feature of JIRA leave the field blank gt Custom 03 This should be set
62. that you will be synchronizing in this project Incident Priority Computer severity Version Status Area Type Release otes Operating System Task Priority Status From this screen you need to click on Priority Status and Type in turn to configure their values a Incident Type Click on the Type hyperlink under Incident Standard Fields to bring up the Incident type mapping configuration screen Bug Change Request Enhancement Incident Issue Limitation Risk Training The table lists each of the incident types available in SpiraTeam and provides you with the ability to enter the matching FogBugz case category ID for each one You can map multiple SpiraTeam fields to the same FogBugz fields e g Bug and Incident in SpiraTeam are both equivalent to Bug in FogBugzZ in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from FogBugz gt SpiraTeam The values for the category ID are fixed for FogBugz and should be Category Name Category ID Bug Feature So depending on which types have been configured in SpiraTeam you ll need to adjust the mapping so that the appropriate SpiraTeam types correspond to the equivalent FogBugz category b Incident Status Click on the Status hyperlink under Incident Standard Fields to bring up the Incident status mapping configuration screen Field Vi Assigned Closed
63. the ID column the one on the left is the value that needs to get added as the External Key inside SpiraTeam b TFS Custom Fields If the custom field in TFS is a list field first you need to go to Administration gt Edit Custom Lists in SpiraTeam and create a new custom list that contains all the different values that are being used in TFS Then for both list fields and value fields you need to go to Administration gt Edit Custom Properties and add a new custom property onto the Requirement artifact type with the name of the appropriate TFS field e g Risk Stack Rank etc and if a list field link it to the custom list you created in the previous step The custom property will now be available for data mapping Now back in the data synchronization data mapping page click on the hyperlink under Requirement Custom Properties that corresponds to the custom property to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping FS Test Project 1 Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the MsTfsDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Risk External Key Microsoft VSTS Common Risk Custom Value Mapping 1 High 2 Medium 3 Low First you need to enter the
64. the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Operating System External Key OperatingSystem Custom Value Mapping Windows 2000 Windows 2000 Windows 2003 Windows NT 4 0 E Windows Vista Windows XP First you need to enter the word OperatingSystem as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Operating System field in Bugzilla Next for each of the Property Values in the table in the lower half of the page you need to enter the Bugzilla name of the various Operating System values that are configured in Bugzilla c Bugzilla s Hardware Field If your instance of Bugzilla requires that all new issues are submitted with a Hardware value then you will need to fill out this section You first need to create an incident custom property in SpiraTeam of type LIST that contains the various hardware platform names that exist inside Bugzilla Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the BugzillaDataSync external
65. the id of the custom field click Update b List Custom Properties This refers to custom properties that are either of type List or Multi List Click on the hyperlink of the list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen For list custom properties there will be a textbox for both the custom field itself and a mapping table for each of the custom property values that need to be mapped Edit Custom Property Data Mapping Redmine Demo Project Change Project lt lt Back to Project Mappings To contigure the data mappings for this custom property please fill in the RedmineDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Custom Property 2 External Key 3 Custom Value Mapping Custom Value 1 Custom Value 2 Yes Value 2 First you need to find the ID of the custom field in Redmine that matches this custom property in Spiraleam This should be entered in the External Key field below the name of the custom property Next for each of the Property Values in the table in the lower half of the page you need to enter the full name not the id this time of the custom field value as specified in Redmine Once you have updated the various mapping sections you are now ready to start the service 11 3 Enabling the
66. the list please click on the Add button instead In either case you will be taken to the following screen where you can enter or modify the OnTime Data Synchronization plug in Edit Plug In OnTimeDataSync lt lt Back to Data Synchronization Home Please enter edit the following information for the plug in The exact information that needs to be entered Is specific to each plug in and you should refer to the documentation for the plug in when entering changing It Name OnTimeDataSync Description Connection Info https mysite axosoft com Login mylogin gmail com Time Offset o hans L Auto Map Users Custom 01 72 2baec5 6b53 40a1 a966 6150d381de05 Custom 02 ykkeWD3eViMJ6WbV1Htkutly wSjS2ahitSbwas Custom 03 408Gp0_ cPh5wTnpwigPLN3 Custom 04 _oCSHPVG5tpFKETHBgxUBKbxXaTzzVgYtKC9 amp Custom 05 You need to fill out the following fields for the OnTime Plug in to operate correctly gt Name this needs to be set to OnTimeDataSync This needs to match the name of the plug in DLL assembly that was copied into the C Program Files SpiraTeam Bin folder minus the dll file extension If you renamed the OnTimeDataSync dll file for any reason then you need to change the name here to match gt gt Description this should be set to a description of the plug in This is an optional field that is used for documentation purposes and is not actually used by the system Connection Info this should t
67. the service entry and choose the option to set the startup type to Automatic This will ensure that synchronization continues between SpiraTeam and TFS after a reboot of the server 5 3 2 Using SpiraTeam with TFS Now that the integration service has been configured and the service started initially any incidents already created in SpiraTeam for the specified projects will be imported into TFS and any requirements tasks or bugs already created in TFS will be imported into SpiraTeam At this point we recommend opening the Windows Event Viewer and choosing the Application Log In this log any error messages raised by the SpiraTeam Data Sync Service will be displayed If you see any error messages at this point we recommend immediately stopping the SpiraTeam service and checking the various mapping entries If you Cannot see any work items with the mapping information we recommend sending a copy of the event log message s to Inflectra customer services Support inflectra com who will help you troubleshoot the problem To use SpiraTeam with TFS on an ongoing basis we recommend the following general processes be followed gt When running tests in SpiraTest or SpiraTeam defects found should be logged through the Test Execution Wizard as normal gt Once an incident has been created during the running of the test it will now be populated across into TFS as a work item of type corresponding to the types setup in the incident type mappi
68. the value that s used on the reverse synchronization from ClearQuest gt SpiraTeam c Incident Severity Click on the Severity hyperlink under Incident Standard Fields to bring up the Incident severity mapping configuration screen Edit standard Field Data Mapping Sample Application Two Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the ClearQuestDataSync plug in next to each Spiraleam value Critical Critical High Mayjar Medium Average Low Minor The table lists each of the incident severities available in SpiraTeam and provides you with the ability to enter the matching ClearQuest severity name for each one You can map multiple SpiraTeam fields to the same ClearQuest fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from ClearQuest gt SpiraTeam 8 2 4 Configuring the Custom Property Mapping Now that the various SpiraTeam standard fields have been mapped correctly we need to configure the custom property mappings This is used for both custom properties in SpiraTeam that map to custom fields in ClearQuest and also for custom properties in SpiraTeam that are used to map to standard fields in ClearQuest e g Project Resolution that don t exist in SpiraTeam From the View Edit Project Data Mapping screen
69. this setting users in SpiraTeam and Redmine are free to have different usernames because you specify the corresponding Redmine name for each user as outlined in section 11 2 2 gt Custom 01 05 these are not currently used by the Redmine data sync plug in and can be left blank 11 2 Configuring the Data Mapping Next you need to configure the data mapping between SpiraTeam and Redmine This allows the various projects users releases incident types statuses priorities and custom property values used in the two applications to be related to each other This is important as without a correct mapping there is no way for the integration service to know that an Duplicate incident in SpiraTeam is the same as a Rejected bug in Redmine for example The following mapping information needs to be setup in Spiraleam The mapping of the project identifiers for the projects that need to be synchronized gt The mapping of users in the system gt The mapping of releases equivalent to Redmine versions in the system gt The mapping of the various standard fields in the system gt The mapping of the various custom properties in the system Each of these is explained in turn below 11 2 1 Configuring the Project Mapping From the data synchronization administration page you need to click on the View Project Mappings hyperlink next to the Redmine plug in name This will take you to the data mapping home page for the
70. to the word True if you want to have the plugin restrict synchronization to only loading new incidents from SpiraTeam gt JIRA and updating existing items This is useful if you want to prevent existing issues in JIRA from being loaded into Spiraleam Leave blank if you want the plugin to synchronize normally gt Custom 04 This should be set to the word True if you want to have the plugin copy file attachments from SpiraTeam gt JIRA This can use additional system resources and may fail if the files are too large for JIRA s API to handle Leave the field blank if you want the default behavior which is to not synchronize attachments gt Custom 05 When you click Force Resync inside SpiraTeam it will attempt to resynchronize all incidents issues from 1 1 1900 Sometimes that causes the JIRA API to timeout or exceed the maximum allowed number of results if there are a large number of existing issues in JIRA You can set this field to a specific year e g 1995 or year and month e g 2010 11 to restrict how far back the system will look for existing issues If you leave this field blank it will use the default value of 1900 01 Note For most users we recommend leaving Custom 01 Custom 05 blank 3 2 Configuring the Data Mapping Next you need to configure the data mapping between SpiraTeam and JIRA This allows the various projects users releases incident types statuses priorities and cust
71. under HTTPS SSL this custom property can be set to determine if the plug in should verify that the SSL certificate is a trusted root certificate Set to True if you are using an SSL certificate that was issued by a trusted Certification Authority and set to False if you are using a self signed certificate Custom 03 05 these are not currently used by the Bugzilla data sync plug in and can be left blank 4 2 Configuring the Data Mapping Next you need to configure the data mapping between Spiraleam and Bugzilla This allows the various projects users releases incident types statuses priorities and custom property values used in the two applications to be related to each other This is important as without a correct mapping there is no way for the integration service to know that an Duplicate incident in SpiraTeam is the same as an UNCONFIRMED bug in Bugzilla for example The following mapping information needs to be setup in SpiraTeam gt gt gt gt gt The mapping of the project identifiers for the projects that need to be synchronized The mapping of users in the system The mapping of releases equivalent to Bugzilla versions in the system The mapping of the various standard fields in the system The mapping of the various custom properties in the system Each of these is explained in turn below 4 2 1 Configuring the Project Mapping From the data synchronization administration p
72. upgrade to at least v2 3 before trying to integrate with JIRA The steps that need to be performed to configure integration with JIRA are as follows gt Download the latest JIRA Data Sync plug in for SpiraTeam from our website gt There are separate plug ins for JIRA 3 x and JIRA 4 x so please make sure you download the correct version gt Setup the plug in in SpiraTeam to point to the correct instance of JIRA gt Configure the data field mappings between SpiraTeam and JIRA gt Start the service and verify data transfer 3 1 1 Download the JIRA Plug in Go to the Inflectra website and open up the page that lists the various downloads available for SpiraT eam http www inflectra com Spiraleam Downloads aspx Listed on this page will be the JIRA Plug In for SpiraTeam Right click on this link and save the Zip compressed folder to the hard drive of the server where SpiraTeam is installed Note There are separate plug ins for JIRA 3 x and JIRA 4 x so please make sure you download the correct version Open up the compressed folder and extract the JiraDataSync dll file and place it in the C Program Files SpiraTeam Bin folder it may be SpiraTest or SpiraPlan depending on which product you re running This folder should already contain the DataSyncService exe and DataSyncService exe config files that are the primary files used for managing the data synchronization between SpiraTeam and other systems If you do not have an on premi
73. values as well Name Area External Key Ares Documentation Miscellaneous User Interface First you need to enter the word Area as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Area field in FogBugz Next for each of the Property Values in the table in the lower half of the page you need to enter the FogBugz ID of the various Areas that are configured in FogBugz The FogBugz Area ID can be found by going to Settings gt Projects and viewing the areas in the project Delete Area Primary Contact Code Project s Primary Contact Documentation Project s Primary Contact Miscellaneous Project s Primary Contact User Interface Project s Primary Contact Create New Area Each project is divided into functional areas You must have at least one area per project Then hover the mouse over the area name The area ID will be displayed in the URL line as ixArea X where X is the numeric ID of the area Once you have updated the various mapping sections you are now ready to start the service 6 3 Enabling the Data Synchronization 6 3 1 Starting the Service When SpiraTeam is installed a Windows Service SpiraTeam Data Sync Service is installed along with the web application However to avoid wasting system resources this service is initially set to run manually To ensure continued synchronization of SpiraTeam with
74. verified and possibly changed are marked in yellow above You need to check the following information gt The polling interval allows you to specify how frequently the data synchronization service will ask Spiraleam and the external system for new data updates The value is specified in milliseconds and we recommend a value no smaller than 5 minutes i e 300 000ms The larger the number the longer it will take for data to be synchronized but the lower the network and server overhead gt The base URL to your instance SpiraTeam It is typically of the form http lt server name gt SpiraTeam Make sure that when you enter this URL on a browser on the server itself the application login page appears gt A valid login name and password to your instance of SpiraTeam This user needs to be a member of the project s that will be synchronized with JIRA and needs to have at least Incident create modify view permissions and Release create modify view permissions in these projects Once you have made these changes save the file and proceed to the next stage 2 1 3 Configuring the Plug In The next step is to configure the plug in within SpiraTeam so that the system knows how to access the JIRA server To start the configuration please open up SpiraTeam in a web browser log in using a valid account that has System Administration level privileges and click on the System gt Data Synchronization administration option from the left hand na
75. will need to upgrade to at least v4 0 before trying to integrate with OnTime The steps that need to be performed to configure integration with OnTime are as follows gt Enable the REST API in OnTime Download the latest OnTime Data Sync plug in for SpiraTeam from our website Setup the plug in in SpiraTeam to point to the correct instance of OnTime Configure the data field mappings between SpiraTeam and OnTime Vv Vv VV V Start the service and verify data transfer 10 1 1 Enable the REST API in OnTime First you will need to login to your instance of OnTime and click on Tools gt System Options Then click on the Axosoft API Settings section System Settings General API Settings Enable API System Labels Pid Wace Manage the API keys for your apps and 3rd party extensions Details Panel View and manage all 3rd party API tokens with access to this account Axosoft API Settings SMTP Server Localization Check the box to Enable API and then click on the Manage API Keys button Edit API Key Spira Client ID Client Secret API Limits Allowed API calls each second Allowed API calls each day API calls made today 1 Cancel On this screen you will need to enter the name of the application you are creating an API key for e g Spira and then record the following two pieces of information e Client ID e Client Secret You will need these later on Then click Save The OnTime Client S
76. you will be synchronizing in this project Requirement Component Importance Status Type Test Case Pronty Incident Component Pronity Severty Status a Scalar Custom Properties This refers to custom properties that have a simple user entered value and don t need to have their specific options mapped between SpiraTeam and OnTime All of the custom property types except List and Multi List fall into this category e g Text Date User Boolean Decimal Integer etc Click on the hyperlink of the text custom property under Incident Custom Properties to bring up the custom property mapping configuration screen For text custom properties there will be no values listed in the lower half of the screen Edit Custom Property Data Mapping OnTime Sample Project C lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the OnTimeDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Artifact Type Incident Name Notes Text PA ad You need to lookup the display name of the custom field in OnTime that matches this custom property in SpiralTeam Once you have entered the id of the custom field click Update b List Custom Properties Click on the hyperlink of the list custom property under Incident Custom Properties to bring up the custom propert
77. 00 Available Effort 184 00 MantisDataSync ID Beta1 1 0 2 8 In addition to the standard fields and custom properties configured for Releases you will see an additional text property called MantisDataSync ID that is used to store the mapped external identifier for the equivalent Release in Mantis The Mantis ID of a version is the string that is in the The Mantis Release ID can be found by going to Manage gt Manage Projects gt Versions and viewing a release s details Edit Project Version Date Order 2009 12 10 13 34 24 Description Update Version The Mantis Release ID is the highlighted text field Copy and paste this into the field in SpiraTeam Depending on your regional settings in both applications this field will likely be case sensitive For versions imported into Mantis from SpiraTeam the Version will have an S appended to the name and for versions in SpiraTeam imported from Mantis the version field of the Release will have M appended to the name 7 2 4 Configuring the Standard Field Mapping Now that the projects user and releases have been mapped correctly we need to configure the standard incident fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the MantisDataSync plug in entry Artifact Field Mapping Please click on each of the links below t
78. Aa o Plan spirafeam spiraPlan ee ay spirafest ee SpiraTeam External Bug Tracking Integration Guide Inflectra Corporation Date October 7th 2015 inflectraZ Contents 8 9 MNrOdUCUOM s essiiicresriisnnseriisisnisinrn 1 Using SpiraTeam with JIRA 5 2 Using SpiraTeam with JIRA 3 4 22 Using SpiraTest with Bugzilla 39 Using SpiraTest with MS TFS 53 Using SpiraTest with FogBugZ 77 Using SpiraTeam with Mantis 92 Using SpiraTeam with ClearQuest105 Using SpiraTeam with IBM RTC 117 10 Using Spira with Axosoft 14 127 11 Using SpiraTeam with Redmine 140 12 Using Spira with OnTime 11 152 Appendix 1 Desktop Data Sync 165 1 Introduction Spiraleam is an integrated Application Lifecycle Management ALM system that manages your project s requirements releases test cases issues and tasks in one unified environment SpiraTeam contains all of the features provided by SpiraTest our highly acclaimed quality assurance system and SpiraPlan our agile enabled project management solution With integrated customizable dashboards of key project information SpiraTeam allows you to take control of your entire project lifecycle and synchronize the hitherto separate worlds of development and testing However many organizations may be already using other bug tracking systems and not want to have to mig
79. As String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name EventLogSource serializeAs String gt lt value gt SpiraTeam Data Sync Service lt value gt lt setting gt lt setting name TraceLogging serializeAs String gt lt value gt False lt value gt lt setting gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt applicationSettings gt lt conftigquration gt The sections that need to be verified and possibly changed are marked in yellow above You need to check the following information gt The polling interval allows you to specify how frequently the data synchronization service will ask Spiraleam and the external system for new data updates The value is specified in milliseconds and we recommend a value no smaller than 5 minutes i e 300 000ms The larger the number the longer it will take for data to be synchronized but the lower the network and server overhead gt The base URL to your instance SpiraTeam It is typically of the form http lt server name gt SpiraTeam Make sure that when you enter this URL on a browser on the server itself the application login page appears gt A valid login name and password to your instance of SpiraTeam This user needs to be a member of the project s that will be synchronized with OnTime and needs to have at least Incident create modify view permissions and Release create modify view permissions in these projects O
80. Data Sync Service lt value gt lt setting gt lt setting name TraceLogging serializeAs String gt lt value gt False lt value gt lt setting gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt applicationSettings gt lt contiquration gt The sections that need to be verified and possibly changed are marked in yellow above You need to check the following information gt The polling interval allows you to specify how frequently the data synchronization service will ask Spiraleam and the external system for new data updates The value is specified in milliseconds and we recommend a value no smaller than 5 minutes i e 300 000ms The larger the number the longer it will take for data to be synchronized but the lower the network and server overhead gt The base URL to your instance SpiraTeam It is typically of the form http lt server name gt SpiraTeam Make sure that when you enter this URL on a browser on the server itself the application login page appears gt Avvalid login name and password to your instance of SpiraTeam This user needs to be a member of the project s that will be synchronized with RTC and needs to have at least Incident create modify view permissions and Release create modify view permissions in these projects Once you have made these changes save the file and proceed to the next stage 9 1 3 Configuring the Plug In The next step is to configure the plug in within Spi
81. Delete This screen lists all the plug ins already configured in the system Depending on whether you chose the option to include sample data in your installation or not you will see either an empty screen or a list of sample data synchronization plug ins If you already see an entry for FogBugzDataSync you should click on its Edit link If you don t see such an entry in the list please click on the Add button instead In either case you will be taken to the following screen where you can enter or modify the FogBugz Data Synchronization plug in Edit Plug In FogBugzDataSync lt lt Back to Data Synchronization Home Please enter edit the following information for the plug in The exact information that needs to be entered is specific to each plug in and you should refer to the documentation for the plug in when entering changing it Name FogBugzDataSync Description Synchronizes incidents with FogBugz Connection Info https mycompany fogbugz com Login myname mycompany com Password Time Offset Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 You need to fill out the following fields for the FogBugz Plug in to operate correctly gt Name this needs to be set to FogBugzDataSync This needs to match the name of the plug in DLL assembly that was copied into the C Program Files SpiraTeam Bin folder minus the dll file extension If you renamed the FogBugzDataSync dll file for any reason
82. Download the latest ClearQuest Data Sync plug in for SpiraTeam from our website Vv Setup the plug in in SpiraTeam to point to the correct instance of ClearQuest gt Configure the data field mappings between Spiraleam and ClearQuest gt Start the service and verify data transfer 8 1 1 Download the ClearQuest Plug In Go to the Inflectra website and open up the page that lists the various downloads available for SpiraTeam http www inflectra com Spiraleam Downloads aspx Listed on this page will be the ClearQuest Plug In for SpiraTeam Right click on this link and save the Zip compressed folder to the hard drive of the server where SpiraTeam is installed Open up the compressed folder and extract the ClearQuestDataSync dll file and place it in the C Program Files SpiraTeam Bin folder it may be SpiraTest or SpiraPlan depending on which product you re running This folder should already contain the DataSyncService exe and DataSyncService exe config files that are the primary files used for managing the data synchronization between Spiraleam and other systems You will then need to install the ClearQuest client application itself onto the SpiraTeam server This is needed because the ClearQuest plugin communicates with the ClearQuest API which is part of the ClearQuest client installation The SpiraTeam plugin will use a single ClearQuest user license when it connects to ClearQuest If you do not have an on premise installation of SpiraTe
83. Edit Project Data Mapping Library Information System Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the BugzillaDataSync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need ta be mapped for the synchronization to operate Project Name Library Information System External Key deleteable Active Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority Resolution severity Notes Status Component yp Operating System Hardware Release Notes Operating System Task a Bugzilla s Component Field If your instance of Bugzilla requires that all new bugs are submitted with a Component then you will need to fill out this section You first need to create an incident custom property in SpiraTeam of type LIST that contains the various component names that exist inside Bugzilla Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property pleas
84. IOS over TCP IP N Provides Telephany API TAPI support For p as hah bhe Cashing amp emonnk Local Systerh Local Service Local Systert maad ase lasal C bam extended Standard Click on the SpiraTeam Data Sync Service entry and click on the link to start the service Then right click the service entry and choose the option to set the startup type to Automatic This will ensure that synchronization continues between SpiraTeam and JIRA after a reboot of the server 2 3 2 Using SpiraTeam with JIRA Now that the integration service has been configured and the service started initially any incidents created in SpiraTeam for the specified projects will be imported into JIRA and any existing issues in JIRA will get loaded into SpiraTeam as either incidents or requirements depending on your configuration At this point we recommend opening the Windows Event Viewer and choosing the Application Log In this log any error messages raised by the SpiraTeam Data Sync Service will be displayed If you see any error messages at this point we recommend immediately stopping the SpiraTeam service and checking the various mapping entries If you cannot see any issues with the mapping information we recommend sending a copy of the event log message s to Inflectra customer services Support inflectra com who will help you troubleshoot the problem To use SpiralTeam with JIRA on an ongoing basis we recommend the followin
85. NFLECTRA Custom 02 Custom 03 Spira Incidentld Custom 04 Spira Detector Custom 05 User Story You need to fill out the following fields for the TFS Plug in to operate correctly gt Name this needs to be set to MsTfsDataSync This needs to match the name of the plug in DLL assembly that was copied into the C Program Files SpiraTeam Bin folder minus the dll file extension If you renamed the MsTfsDataSync dll file for any reason then you need to change the name here to match gt Description this should be set to a description of the plug in This is an optional field that is used for documentation purposes and is not actually used by the system gt Connection Info this should the URL that you use for connecting Visual Studio to the Team Foundation Server gt For TFS 2005 2008 it is of the format http servername 8080 gt For TFS 2010 it is of the format http servername 8080 tfs collectionname where collectionname is the name of the project collection you re integrating with gt Login this should be set to a valid user that has permissions to access the TFS installation The login needs to have permissions to create and view work items and iterations within TFS Note Do not include the Windows Active Directory Domain in this field if you are using a Windows domain user gt Password this should be set to the password of the user specified above gt Time Offset normally this should be set t
86. New in TFS in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from TFS gt SpiraTeam We recommend that you always point the New and Open statuses inside SpiraTeam to point to the Active New TFS state reason and make Open in SpiraTeam the Primary status of the two This is recommended so that as new incidents in SpiraTeam get synched over to TFS they will get switched to the Active New status in TFS which will then be synched back to Open in SpiraTeam That way you ll be able to see at a glance which incidents have been synched with TFS and those that haven t c Incident Priority Click on the Priority hyperlink under Incident Standard Fields to bring up the Incident Priority mapping configuration screen 1 Critical Yes 2 High Yes 3 Medium Yes 4 Low Yes The table lists each of the incident priorities available in SpiraTeam and provides you with the ability to enter the matching TFS priority value for each one To make this easier we recommend that inside the Administration gt Edit Incident Priorities screen you first make any statuses not used in TFS inactive in SpiraTeam d Incident Severity TFS 2012 plugin only Click on the Severity hyperlink under Incident Standard Fields to bring up the Incident Severity mapping configuration screen 1 Critical 2 High 3 Medium 4 Low The
87. Plan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with the JIRA issue bug tracking system versions 3 0 4 0 The built in integration service allows the quality assurance team to manage their requirements and test cases in SpiraTeam execute test runs in SpiraTest and then have the new incidents generated during the run be automatically loaded into JIRA Once the incidents are loaded into JIRA as issues the development team can then manage the lifecycle of these issues in JIRA and have the status changes in JIRA be reflected back in Spiraleam In addition if you are using JIRA 4 x or higher any issues logged directly into JIRA will get imported into Spiraleam so that they can be linked to test cases and requirements 3 1 Configuring the Integration Service This section outlines how to configure the integration service to export incidents into JIRA and pick up subsequent status changes in JIRA and have them update SpiraTeam It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam and a working installation of JIRA The following versions of SpiraTeam and JIRA are supported gt The JIRA 5 x plugin supports JIRA 5 0 or later and SpiraTeam v4 0 or later see section 2 gt The JIRA 4 x plugin supports JIRA 4 0 or later and SpiraTeam v3 0 or later gt The JIRA 3 x plugin supports JIRA 3 0 or later and SpiraTeam v2 3 or later If you have an earlier version of SpiraTeam you will need to
88. Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Requirement Importance Status Test Case Priority Incident Priority Custom Date Severity Free Text Field Status Multi Select Field Type Single Select List Custom User Components Environment Release Task Priority Status If the project name does not match the name of the project you want to configure the data mapping for click on the Change Project hyperlink to change the current project To enable this project for data synchronization with JIRA you need to enter gt External Key This should be set to the name of the project Key in JIRA Typically this is a short acronym for the project Projects as Project list Jb Add Project Name Key URL Project Lead Default Assignee Operations Demonstration Administrator Project Lead Edit Delete Active Flag Set this to Yes so that SpiraTeam knows that you want to synchronize data for this project Once the project has been completed setting the value to No will stop data synchronization reducing network utilization Click Update to confirm these settings Once you have enabled the project for data synchronization you can now enter the other data mapping values outlined below Note Once you have successfully configured the project when creating a new project you should c
89. Release ID is the highlighted text field Copy and paste this into the field in SpiraTeam Depending on your regional settings in both applications this field will likely be case sensitive You can map multiple SpiraTeam fields to the same Mantis fields e g Bug and Incident in SpiraTeam are both equivalent to category development in Mantis In a situation like this enter in the Mantis category in both Big and Incident external keys and decide which one will be primary For issues coming from Mantis into SpiraTeam the one marked Primary will be used and for issues being created in Mantis the same category will be used to create the issue b Incident Status The Incident Status is an optional field to be linked to the Mantis field by the same name If you do not link values then defaults will be used For issues coming from Mantis into SpiraTeam incidents will be marked as New as defined by the View Edit Status in Administration and for issues being transferred to Mantis the default is new Note that if an issue has an Owner in SpiraTeam then the default for the new issue in Mantis is assigned For existing issues updates to the field will not be transferred over Not Reproducible Yes The table lists each of the incident types available in SpiraTeam and provides you with the ability to enter the matching Mantis Category for each one The values to put in External Key is any one of the Status v
90. SpiraTeam Data Sync Service Name Description Status Startup Type Log On As Sy Secunty Accounts Manager Stores security information for local user acc Started Atomatic Local System Start the service Sy Security Center Monitors system security settings and config Automatic Local Systern Server Supports File print and namedpipe sharing Started Automatic Local System Description By Shel Hardware Detection Provides notifications For AutoPlay hardware Started Aukornatic Local System oe ed homeo A Sia Simple Mail Transfer Protocol SMTP Transports electronic mail across the network Local System systems Smart Card Manages access to smart cards read by this Local Service ty SpiraTeam Data Syne Service Manages the etween By SQLAgentsSPIRA Hy SOLSERVERAGENT amp 550e Discovery Service Enables cescovery of UPn devices on your h Local Service Sy System Event Notification Tracks system events such as Windows laga Local System hy System Restore Service Performs system restore functions To stop Local System Sf Task Scheduler Enables a user to configure and schedule au j Local Systerh My TCP IP NetBIOS Helper Enables support For NetBIOS over TCP IP N Local Service Provides Telephany API TAPI support For p Local Systert omen ke as ha h ie laraj C ibam Cashia maada amram extended Standard Click on the SpiraTeam Data Sync Service entry and click on the link to start the service Then right click
91. Sync plug in you need to enter the login for this username in Bugzilla This will allow the data synchronization plug in to Know which user in SpiraTeam match which equivalent user in Bugzilla Click Update once you ve entered the appropriate login name You should now repeat for the other users who will be active in both systems 4 2 3 Configuring the Release Mapping Now that the projects and users have been mapped correctly we need to configure the mapping between Releases Iterations in SpiraTeam and Versions in Bugzilla To do this please navigate to Planning gt Releases and click on the Release Iteration in question Make sure you have the Overview tab visible and expand the Details section of the release iteration Release 3 3 0 0 0 Release 3 0 RL 000020 Name Release 3 0 Overview Incidents Regs amp Tasks Test Cases Test Runs Attachments History Y Details H Version 0 0 Creator System Administrator v Start End Date A Creation Date 6 5 2013 5 49 11 PM Resources Active Yes v Non Working person days Iteration Plan Effort 184 00 Available Effort 184 00 BugzilaDataSync ID In addition to the standard fields and custom properties configured for Releases you will see an additional text property called BugzillaDataSync ID that is used to store the mapped external identifier for the equivalent Version in Bugzilla You need to enter the name of the equivalent v
92. Two Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the RtcDataSync plug in you need to specify the keyid of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Sample Application Two External Key Test Project Change Management Active f i e Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority severity Status Release Task Priority status From this screen you need to click on Status and Type in turn to configure their values a Incident Status Click on the Status hyperlink under Incident Standard Fields to bring up the Incident status mapping configuration screen Edit Standard Field Data Mapping Sample Application Two Change Project lt lt Back to Project Mappings To configure the data mappings for this fleld please fill in the external key values for the RtcDataSyne plug in next to each Spiraleam value m pai al Assigned Closed Complete a Duplicate al Mew Plew a Mot Reproducible Invelidate Open start Working Reopen Resolved Complete I The table lists each of the incident statuses available in
93. Windows Service control panel niu Services Fle Action View Help Beoe AM gt Gy Services Local i Services Local SpiraTeam Data Sync Service Start the service Description Manages the data synchronization between SpiraTeam and other external systems Name Sy Secunty Accounts Manager By Security Center egy Server Sa Shell Hardware Detection Sia Simple Mail Transfer Protocol SMTP By Smart Card th SpiraTeam Data Syne Service By SQLAgentsSPIRA Sy SOLSERVERAGENT By SSOP Discovery Service Siy System Event Notification By System Restore Service Description Stores security information For local user acc Monitors system security settings and config Supports File print and named pipe sharing Provides notifications For AutoPlay hardware Transports etachronic mail across the network Manages access to smart cards read by this Enables cescovery of UPn devices on your h Tracks system events such as Windows laga Performs system restore functions To stop Status Started Started Started Startup Type Aornatic Automatic Automatic Akomatic Manual Maral Lag On As Local System Local Systern Local System Local System Local System Local Service beat Spa Local System Local Systern Local Service Local Systern Local System Sy Task Scheduler Sy TCP IP NetBIOS Helper Siy Telephony ae Talas Enables a user to configure and schedule au Enables support For NetB
94. Workflow Settings Due Dat i Incident Workflow Settings Project Status acive wd Escalation Settings The ID of the project is the value listed in the browser URL directly after the Projectld text In the example above the project ID would be 3 gt Active Flag Set this to Yes so that SpiraTeam knows that you want to synchronize data for this project Once the project has been completed setting the value to No will stop data synchronization reducing network utilization Click Update to confirm these settings Once you have enabled the project for data synchronization you can now enter the other data mapping values outlined below Note Once you have successfully configured the project when creating a new project you should choose the option to Create Project from Existing Project rather than Use Default Template so that all the project mappings get copied across to the new project 12 2 2 Configuring the User Mapping To configure the mapping of users in the two systems you need to go to Administration gt Users gt View Edit Users which will bring up the list of users in the system Then click on the Edit button for a particular user that will be editing defects in OnTime Add Edit User Fred Bloggs Please review the information listed below and make any changes if necessary Once you have finished click Update Insert to confirm them First Name Middle Initial La
95. aTeam and TFS This allows the various projects users releases incident types statuses priorities and custom property values used in the two applications to be related to each other This is important as without a correct mapping there is no way for the integration service to know that a Not Reproducible incident in SpiraTeam is the same as a Closed Cannot Reproduce bug work item in TFS for example The following mapping information needs to be setup in SpiraTeam gt The mapping of the project identifiers for the projects that need to be synchronized The mapping of users in the system The mapping of releases equivalent to TFS iterations in the system The mapping of the various standard incident fields in the system The mapping of the various custom incident properties in the system The mapping of the various standard requirement fields in the system if synching requirements Vv VV V yY The mapping of the various custom requirement properties in the system if synching requirements gt The mapping of the various standard task fields in the system if synching tasks gt The mapping of the various custom task properties in the system if synching tasks Note If using SpiraTest you do not need to setup the last two sets of mappings as Tasks are not available in SpiraTest 5 2 1 Configuring the Project Mapping From the data synchronization administration page you need to click on the View Project Mappings
96. aTeam and provides you with the ability to enter the matching OnTime severity name for each one You can map multiple SpiraTeam fields to the same OnTime fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from OnTime gt SpiraTeam Note The OnTime external key needs to exactly match the display name of the severity inside OnTime If you change the name of a severity in OnTime you ll need to update the value in the data mapping configuration as well 12 2 5 Configuring the Custom Property Mapping Now that the various SpiraTeam standard fields have been mapped correctly we need to configure the custom property mappings This is used for both custom properties in SpiraTeam that map to custom fields in OnTime and also for custom properties in SpiraTeam that are used to map to standard fields in OnTime currently only Replication Procedures that don t exist in SpiraTeam From the View Edit Project Data Mapping screen you need to click on the name of the Incident Custom Property that you want to add data mapping information for We will consider the three different types of mapping that you might want to enter OnTimeDataSync Project Data Mapping Sample OnTime Project Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the OnTimeData Sync plug in you need to specify the key id of t
97. acking functionality of Microsoft Visual Studio Team System MS VSTS Team Foundation Server TFS hereafter referred to as TFS The built in integration service allows the quality assurance team to manage their requirements and test cases in Spiraleam execute test runs in SpiraTest and then have the new incidents generated during the run be automatically loaded into TFS Once the incidents are loaded into TFS as work items the development team can then manage the lifecycle of these work items in TFS and have the status changes in TFS be reflected back in SpiraTeam Similarly as the requirements are decomposed into discrete project tasks in SpiraPlan the integration service will automatically load these new tasks into TFS as task work items where the development team can manage their lifecycle with schedule and progress changes in TFS being reflected back in SpiraTeam 5 1 Configuring the Integration Service This section outlines how to configure the integration service to export incidents and tasks into TFS and pick up subsequent status changes in TFS and have them update SpiraTeam It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam and a working installation of TFS There are different plugins on the Inflectra website that are compatible with different version of SpiraTeam and TFS e The MS TFS 2005 2008 plugin is compatible with SpiraTeam v2 2 and TFS 2005 or 2008 e The MS TFS 2010 plugin is com
98. age 11 1 3 Configuring the Plug In The next step is to configure the plug in within SpiraTeam so that the system knows how to access the Redmine server To start the configuration please open up SpiraTeam in a web browser log in using a valid account that has System Administration level privileges and click on the System gt Data Synchronization administration option from the left hand navigation Data Synchronization Refresh SpiraTeam is able to communicate with a variety of external systems and applications using its background data synchronization service and library of available plug ins This page allows you to view add and modify the list of plug ins make changes to their configuration and verify the status of the most recent synchronization In addition you can force a particular plug in to perform a complete data synchronization by resetting its date of last sync Data Mapping Last SyncDate BugzillaDataSync gt View Project Mappings Not Run gt Force Re Sync Edit Delete View Errors FogBugzDataSync gt View Project Mappings Not Run gt Force Re Sync Edit Delete View Errors JiraDataSync gt View Project Mappings Not Run gt Force Re Sync Edit Delete View Errors MsTfsDataSync gt View Project Mappings Not Run gt Force Re Sync Edit Delete View Errors This screen lists all the plug ins already configured in the system Depending on whether you chose the option to include sample data
99. age you need to click on the View Project Mappings hyperlink next to the Bugzilla plug in name This will take you to the data mapping home page for the currently selected project View Edit Project Data Mapping Library Information System Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the BugzillaDataSync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Library Information System External Key deleteable Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority Resolution severity Notes Status Component Operating System Hardware Release Notes Operating System Task If the project name does not match the name of the project you want to configure the data mapping for click on the Change Project hyperlink to change the current project To enable this project for data synchronization with Bugzilla you need to enter gt External Key This should be set to the name of the equivalent Product in Bugzilla gt Active Flag Set this to Yes so that SpiraTeam knows that you want to synchronize data for this project Onc
100. allation of SpiraTeam but instead are using a hosted subscription provided by Inflectra or a third party company you will not have access to the DataSyncService background service In such situations you should use the Desktop DataSync application instead This application is described in Appendix 1 and can be used instead of the server based DataSyncService 12 1 3 Configuring the Service To configure the integration service please open up the DataSyncService exe config file located in C Program Files SpiralTeam Bin with a text editor such as Notepad Once open it should look like lt xml version 1 0 encoding utf 8 gt lt CONLIOQUraL LOn gt lt COnTIOSect icons lt sectionGroup name applicationSettings type System Configuration ApplicationSettingsGroup System Version 2 0 0 0 Culture neutral PublicKeyToken b77a5c561934e089 gt lt section name Inflectra SpiraTest DataSyncService Properties Settings type System Configuration ClientSettingsSection System Version 2 0 0 0 Culture neutral PublickeyToken b77a5c561934e089 requirePermission false gt lt sectionGroup gt lt configSections gt lt applicationSettings gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt setting name PollingInterval serializeAs String gt lt value gt 600000 lt value gt lt setting gt lt setting name WebServiceUrl serializeAs String gt lt value gt http localhost SpiraTeam lt value gt lt
101. alues in Mantis By default in Mantis the available statuses are Status Projection acknowledged confirmed assigned resolved closed The Mantis values are in the highlighted text field Type these into the External Key field in SpiraTeam Depending on your regional settings in both applications this field will likely be case sensitive You can map multiple SpiraTeam fields to the same Mantis fields just like the Incident Type above c Incident Priority amp Severity The Incident Priority and Severity are optional fields that are linked to Mantis fields by the same name If you do not link values then defaults will be used For issues coming from Mantis into SpiraTeam incidents will leave those fields undefined unset For issues coming from SpiraTeam into Mantis the default priority of normal and severity of minor is used For existing issues updates to the field will not be transferred over 1 Critical Yes immediate Yes 2 High Yes igh Yes 3 Medium Yes normal Yes T 4 Low Yes Yes 1 Critical Yes crash 3 Medium Yes minor a 4 Low Yes trivial Yes The table lists each of the priorities available in SpiraTeam and provides you with the ability to enter the matching Mantis priority for each one The table for Severities has the same functionality The values to put in External Key are any one of the Priority or Severity values in Mantis By default in Mantis the
102. am but instead are using a hosted subscription provided by Inflectra or a third party company you will not have access to the DataSyncService background service In such situations you should use the Desktop DataSync application instead This application is described in Appendix 1 and can be used instead of the server based DataSyncService 8 1 2 Configuring the Service To configure the integration service please open up the DataSyncService exe config file located in C Program Files Spiraleam Bin with a text editor such as Notepad Once open it should look like lt xml version 1 0 encoding utf 8 gt COnriguraction gt lt configSections gt lt sectionGroup name applicationSettings type System Configuration ApplicationSettingsGroup System Version 2 0 0 0 Culture neutral PublicKeyToken b77a5c561934e089 gt lt section name Inflectra SpiraTest DataSyncService Properties Settings type System Configuration ClientSettingsSection System Version 2 0 0 0 Culture neutral PublickeyToken b77a5c561934e089 requirePermission false gt lt sectionGroup gt lt configSections gt lt applicationSettings gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt setting name PollingInterval serializeAs String gt lt value gt 600000 lt value gt lt setting gt lt setting name WebServiceUrl serializeAs String gt lt value gt http localhost SpiraTeam lt value gt lt setting gt lt setti
103. an item in your list in Spiraleam then in the associated field in Mantis Windows must be an available item as well In instances where there is no match then the default will be used in either system On a Multiselection type field for importing back into SpiraTeam only the first top selected value will be stored SpiraTeam List to Mantis Numeric Float Date Text or Email In this case the text value of the SpiraTeam list will be assigned to the Mantis field and values must be exact For example if you linked a SpiraTeam List to a Mantis Date field the value for the List must be a valid date like 1 1 2010 If any value fails the Mantis validation the value will be ignored and the custom field will be set blank or to default When transferring a value back from Mantis into SpiraTeam the text must equal an available item in the custom list or the field will be left blank SpiraTeam Text to Mantis Numeric Float Date Text or Email In this case text will be copied over as is Note that in some special cases like the number date and e mail fields Mantis may apply formatting or verification on values transferred over SpiraTeam Text to Mantis Enum List or Multiselection When pulling data from Mantis the Spiraleam custom field will be translated as the field in Mantis displays However when transferring data to Mantis if the t
104. and Mantis This allows the various projects users releases incident types statuses priorities and custom property values used in the two applications to be related to each other This is important as without a correct mapping there is no way for the integration service to know that an Enhancement in SpiraTeam is the same as a Feature in Mantis for example The following mapping information needs to be setup in SpiraTeam gt gt gt gt gt The linking between the project in SpiraTeam and the project in Mantis The linking of users between the two systems The linking of releases between the two systems The linking of standard SpiraTeam fields to Mantis fields The linking of custom SpiraTeam fields to Mantis custom fields Each of these is explained in turn below 7 2 1 Configuring the Project Mapping While working in the project you want to map from the data synchronization administration page you need to click on the View Project Mappings hyperlink next to the Mantis plug in name This will take you to the data mapping overview page View Edit Project Data Mapping Sample Application Two Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the Mantis Data Sync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be m
105. and view issues and versions within Mantis for the projects that you will be syncing to SpiraTeam gt Password this should be set to the password of the login specified above Time Offset The time offset between the two servers if the Mantis server is on a different server than SpiraTeam For example if the Mantis server s clock is set to Pacific Standard Time PST and the SpiraTeam server is set to Eastern Standard Time EST the Mantis server would be three hours behind SpiraTeam so you would need to put 3 into this field Auto Map Users If enabled and a mapped user is not found between the two systems a search will be made comparing logins between Spiraleam and Mantis for matching UserlDs If one is found than that user will be used If not enabled and a match is not found then the UserID used will be the connecting user for the Data Sync The SpiraTeam User for issues coming into Spiraleam and the Mantis Login for issues imported into Mantis Custom 01 This field specifies whether or not a Resolution item in SpiraTeam or a Note item in Mantis will be created when an issue is created in either system for a new issue Valid values are True or False Default or blank is True Custom 02 This field indicates whether or not to convert Carriage Returns and spaces in Mantis issues when synchronizing them into SpiraTeam If enabled then carriage returns will be converted to HTML breaks and multiple spaces will be
106. ap Users option in the JIRA plugin you can skip this section completely 2 2 3 Configuring the Release Mapping When the data synchronization service runs when it comes across a release iteration in SpiraTeam that it has not seen before it will create a corresponding Version in JIRA Similarly if it comes across a new Version in JIRA that it has not seen before it will create a new Release in SpiraTeam Therefore when using both systems together it is recommended that you only enter new Releases Versions in one system and let the data synchronization service add them to the other system However you may start out with the situation where you already have pre existing Releases Version in both systems that you need to associate in the data mapping If you don t do this you may find that duplicates get created when you first enable the data synchronization service Therefore for any Releases Iterations that already exist in BOTH systems please navigate to Planning gt Releases and click on the Release Iteration in question Make sure you have the Overview tab visible and expand the Details section of the release iteration Release 611 0 1 0 RL 000071 Name Overview Incidents Regs amp Tasks Test Cases Test Runs Attachments History gt Details Start End Date w203 FE i 452013 A Creation Date 4 11 2013 4 58 16 PM Resources 1 Active Yes 7 Non Working fi person days lteratio
107. apped for the synchronization to operate Project Name Sample Application Two Actives Yes Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Release Task Priority If the project name does not match the name of the project you want to configure the data mapping for click on the Change Project hyperlink to change the current project To enable this project for data synchronization with Mantis you need to enter gt External Key This should be set to the ID of the project in Mantis To get the ID of the Project in Mantis log in as an administrator and go to Manage gt Manage Projects Projects Create New Project Name amp Status Enabled Library System development x Sample Application 2 development x Then hover the mouse over the project name The project ID will be displayed in the URL line as project_id x where x is the numeric ID of the project gt Active Flag Set this to Yes so that SpiraTeam knows that you want to synchronize data for this project Once the project has been completed setting the value to No will stop data synchronization reducing network utilization Click Update to confirm these settings Once you have enabled the project for data synchronization you can now enter the other data mapping values outlined
108. apping To configure the mapping of users in the two systems you need to go to Administration gt Users gt View Edit Users which will bring up the list of users in the system Then click on the Edit button for a particular user that will be editing issues in ClearQuest Add Edit User Joe F Smith Please review the information listed below and make any changes if necessary Once you have finished click Update Insert to confirm them First Name Middle Initial Last Name User Hame Department Email Address joesmith mycompany com Emails Enabled Yes V System Administrator No Active User Ye T RSS Token Enable RSS Feeds 411 E66 3 2 CSE 403 GB4E S6FSE 2B EFCH Generate New Project Membership Passwords amp Security TeertrreDar Eme D You will notice that in the Data Mapping tab for the user there is a list of all the configured data synchronization plug ins In the text box next to the ClearQuest Data Sync plug in you need to enter the login for this username in ClearQuest This will allow the data synchronization plug in to know which user in SpiraTeam match which equivalent user in ClearQuest Click Update once you ve entered the appropriate login name You should now repeat for the other users who will be active in both systems 8 2 3 Configuring the Standard Field Mapping Now that the projects user and releases have been mapped correctly we need to configure th
109. assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam v2 3 or later and a working installation of OnTime 2010 or later If you have an earlier version of SpiraTeam you will need to upgrade to at least v2 3 before trying to integrate with OnTime The steps that need to be performed to configure integration with OnTime are as follows Install and configure the OnTime SDK if you have not already done so Download the OnTime11 Data Sync plug in for SpiraTeam from our website Setup the plug in in SpiraTeam to point to the correct instance of OnTime Configure the data field mappings between SpiralTeam and OnTime v VV y Start the service and verify data transfer 12 1 1 Install and Configure the OnTime SDK The API for accessing OnTime remotely is a separate download from the main OnTime application and should be downloaded and installed from AxoSoft s website onto your OnTime server It typically adds a separate IIS virtual directory e g http servername OnTimeSdk to the existing OnTime virtual directory e g http servername OnTime Please make sure you have both virtual directories listed in IIS before continuing Once you have installed the OnTime SDK you need to navigate to the location that it was installed typically C inetoub wwwroot OnTimeSdk and open up the Web Config file in Notepad and locate the appSettings part of the file lt appSettings gt lt add key ConnectionString value
110. at needs to get added as the External Key inside SpiraTeam b TFS Custom Fields lf the custom field in TFS is a list field first you need to go to Administration gt Edit Custom Lists in SpiraTeam and create a new custom list that contains all the different values that are being used in TFS Then for both list fields and value fields you need to go to Administration gt Edit Custom Properties and add a new custom property onto the Task artifact type with the name of the appropriate TFS field e g Discipline Stack Rank etc and if a list field link it to the custom list you created in the previous step The custom property will now be available for data mapping Now back in the data synchronization data mapping page click on the hyperlink under Task Custom Properties that corresponds to the custom property to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping TFS Test Project 1 Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the MsTisDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Discipline External Key icrosoft VSTS Common Discipline Custom Value Mapping Project Management Release Management Release Management First you need to enter the full Reference
111. atically in SpiraTeam In essence SpiraTeam acts as a read only viewer of these incidents You are now able to perform test coverage and incident reporting inside SpiraTest SpiraTeam using the test cases managed by SpiraTest Spiraleam and the incidents managed on behalf of SpiraTest SpiraTeam inside RTC 10 Using Spira with Axosoft 14 This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with the OnTime defect tracking system from AxoSoft hereafter called OnTime The built in integration service allows the quality assurance team to manage their requirements and test cases in Spiraleam execute test runs in SpiraTest and then have the new incidents generated during the run be automatically loaded into OnTime Once the incidents are loaded into OnTime as defects the development team can then manage the lifecycle of these defects in OnTime and have the status changes in OnTime be reflected back in SpiraTeam 10 1 Configuring the Integration Service This section outlines how to configure the integration service to export incidents into OnTime and pick up subsequent status changes in OnTime and have them update SpiraTeam It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam v4 0 or later and a working installation of AxoSoft OnTime 14 or later either hosted in the cloud or on premise If you have an earlier version of Spiraleam you
112. be displayed If you see any error messages at this point we recommend immediately stopping the service and checking the various mapping entries If you cannot see any issues with the mapping information we recommend sending a copy of the event log message s to Inflectra customer services Support inflectra com who will help you troubleshoot the problem To use SpiraTeam with Redmine on an ongoing basis we recommend the following general processes be followed gt When running tests in SpiraTeam defects found should be logged through the Test Execution Wizard as normal gt Developers can log new defects into either SpiraTeam or Redmine In either case they will get loaded into the other system gt Once created in one of the systems and successfully replicated to the other system the incident should not be modified again inside SpiraTeam gt All data changes to the issue should be made inside Redmine gt To enforce this you can modify the workflows set up in SpiraTeam so that the various fields are marked as inactive for all the incident statuses other than the New status gt This will allow someone to submit an incident in SpiraTeam but will prevent them making changes in conflict with Redmine after that point gt As the issue progresses through the Redmine workflow changes to the status priority tracker and target version will be updated automatically in SpiraTeam and any notes added will be added to Spiral
113. ble in the lower half of the page you need to enter the JIRA ID of the various Components that are configured in JIRA The external ID can be found by looking at the URL inside JIRA which choosing to View Edit the component name description d JIRA s Resolution Field If you would like the values of the JIRA Resolution field to be synchronized back to SpiraTeam then you will need to fill out this section You first need to create an incident custom property in SpiraTeam of type LIST that contains the various resolution names that exist inside JIRA Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Sample JIRA Project Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name JIRA Resolution External Key Resolution Custom Value Mapping Cannot Reproduce hii sia First you need to enter the word Resolution as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Resolution field in JIRA Next for each of the Property Val
114. button instead In either case you will be taken to the following screen where you can enter or modify the Mantis Data Synchronization plug in Edit Plug In MantisDataSync lt Back to Data Synchronization Home Please enter edit the following information for the plug in The exact information that needs to be entered is specific to each plug in and you should refer to the documentation for the plug in when entering changing it Name Description Connection hitp tsqmadness com mantis Info Login 5 Time Offset fo Auto liap Users Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 You need to fill out the following fields for the Mantis Plug in to operate correctly gt Name this needs to be set to MantisDataSync This needs to match the name of the plug in DLL assembly that was copied into the C Program Files SpiraTeam Bin folder minus the dll file extension If you renamed the MantisDataSync dll file for any reason then you need to change the name here to match gt Description this should be set to a description of the plug in This is an optional field that is used for documentation purposes and is not actually used by the system gt Connection Info this should the URL that you use to access your instance of Mantis e g https www mycompany com bugs gt Login this should be set to a valid login to the Mantis installation The login needs to have permissions to create
115. cService exe config files that are the primary files used for managing the data synchronization between Spiraleam and other systems If you do not have an on premise installation of SpiraTeam but instead are using a hosted subscription provided by Inflectra or a third party company you will not have access to the DataSyncService background service In such situations you should use the Desktop DataSync application instead This application is described in Appendix 1 and can be used instead of the server based DataSyncService If you have a 64 bit server you will need to also download from our website the specially compiled 32 bit version of the DataSyncService exe file since TFS is a 32 bit application whereas the standard DataSyncService executable is 64 bit Please see KB14 in the Inflectra Support Knowledge Base http www inflectra com Support KnowledgeBase KB14 aspx for details 5 1 2 Configuring the Service To configure the integration service please open up the DataSyncService exe config file located in C Program Files Spiraleam Bin with a text editor such as Notepad Once open it should look like lt xml version 1 0 encoding utf 8 gt lt COnri guration lt configSections gt lt sectionGroup name applicationSettings type System Configuration ApplicationSettingsGroup System Version 2 0 0 0 Culture neutral PublicKeyToken b77a5c561934e089 gt lt section name Inflectra SpiraTest DataSyncService Properties Se
116. cker ID for each one You can map multiple SpiraTeam fields to the same Redmine tracker values in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from Redmine gt SpiraTeam 11 2 5 Configuring the Custom Property Mapping Now that the various SpiraTeam standard fields have been mapped correctly we need to configure the custom property mappings This is used for custom properties in SpiraTeam that map to custom fields in Redmine You will need to first make sure that the custom properties and associated custom lists have been created in both systems Edit Custom Properties Redmine Demo Project Change Project The following custom properties are currently defined for the selected artifact type To view the custom properties for a different artit below You can add edit or remote custom property definitions by clicking the appropriate link in the grid below Property Name Legacy Name Actions Custom Property 1 TEXT 01 gt Edit Definition Remove Custom Property 2 LIST 01 gt Edit Definition Remove From the View Edit Project Data Mapping screen you need to click on the name of the Incident Custom Property that you want to add data mapping information for Project Name Redmine Demo Project External Key spira redmine demo project Active Artifact Field Mapping Please click on each of the links below to configure the ftield lev
117. click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping JIRA DEMO Project Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name JIRA Key External Key JiralssueKey All you need to do on this screen is enter the word JiralssueKey in the External Key textbox and the data sync plug in will know that this custom property is mapped to the built in Issue Key field in JIRA Once you have updated the various mapping sections you are now ready to start the service 2 3 Enabling the Data Synchronization 2 3 1 Starting the Service When SpiraTeam is installed a Windows Service SpiraTeam Data Sync Service is installed along with the web application However to avoid wasting system resources this service is initially set to run manually To ensure continued synchronization of SpiraTeam with JIRA we recommend starting the service and setting its startup type to Automatic To make these changes open up the Windows Control Panel click on the Administrative Tools link and then choose the Services option This will bring up the
118. converted to non breaking spaces to preserve formatting when importing into SpiraTeam If disabled then carriage returns and spaces will be left as is Valid values are True or False Default or blank is True Custom 03 This field is only used when Auto Map Users is enabled and for Incidents synchronized from SpiraTeam into Mantis If enabled and the Auto Map User did not find a user with a matching Login ID then the Login ID will be set to the User in Spira even if that user may not exist in Mantis Depending on Mantis configuration the user may be accepted or it may default back to the Mantis UserID that the Data Sync runs under Valid values are True or Fal se Default or blank is False Custom 04 If enabled this option specifies whether or not to append the Additional Information and Steps To Reproduce fields to the end of the Description field in Spira During transfer of new issues from Mantis to SpiraTeam the Description field in SpiraTeam will consist of the Description field in Mantis appended by the Additional Information field in Mantis and finally the Steps To Reproduce field in Mantis If this option is disabled only the Description will be transferred over Valid values are True or False Default or blank is False Custom 05 This is not currently used by the MantisDataSync and can be left blank 7 2 Configuring the Data Mapping Next you need to configure the data mapping between SpiraTeam
119. ct Incident Priority ReplicationProcedures severity OnTime Operating System Status OnTime Environment Type Release Task Priority Status If the project name does not match the name of the project you want to configure the data mapping for click on the Change Project hyperlink to change the current project To enable this project for data synchronization with OnTime you need to enter gt External Key This should be set to the numeric ID of the project token in OnTime You can find this in OnTime by selecting the project in the project explorer inside OnTime and then clicking the Edit icon This brings up the project details screen Go hd le http localhost OnTime Projects AddEditProject aspx ProjectId 3 gt 4 X vahoo Search File Edit View Favorites Tools Help We d Gontime web Edition a Gy Software for Software Development Home View Defects Features Tasks Incidents Reports Tools Edit Project Corporate Web Site Project Info Project Settings Type General vi Personnel El Field Template Settings Parent Project ROOT LEVEL PROJECT 7 p Defect Field Template Settings prouet Harini Corporate wak are M Feature Field Template Settings ln ii Project Description i peTask Field Template Settings 100 characters max Incident Field Template Settings workflow Settings Defect workflow Settings Feature Workflow Settings Start Date 3 16 2010 Hal Task
120. d to be performed to configure integration with RTC are as follows Download the latest RTC Data Sync plug in for SpiraTeam from our website v Setup the plug in in SpiraTeam to point to the RTC application server gt Configure the data field mappings between SpiraTeam and RTC gt Start the service and verify data transfer 9 1 1 Download the RTC Plug In Go to the Inflectra website and open up the page that lists the various downloads available for SpiraTeam htto www inflectra com SpiraTeam Downloads aspx Listed on this page will be the RTC Plug In for Spiraleam Right click on this link and save the Zip compressed folder to the hard drive of the server where SpiraTeam is installed Open up the compressed folder and extract the RtcDataSync dll file and place it in the C Program Files SpiraTeam Bin folder it may be SpiraTest or SpiraPlan depending on which product you re running This folder should already contain the DataSyncService exe and DataSyncService exe config files that are the primary files used for managing the data synchronization between Spiraleam and other systems If you do not have an on premise installation of SpiraTeam but instead are using a hosted subscription provided by Inflectra or a third party company you will not have access to the DataSyncService background service In such situations you should use the Desktop DataSync application instead This application is described in Appendix 1 and can be used ins
121. d with JIRA and those that haven t The JIRA ID can be found by looking at the URL inside JIRA when choosing to View Edit the Issue Status The URL will include the section id X where X is the numeric ID of the Issue Status inside JIRA Status Details Mode Workflows Operations 4 Open Active jira Edit The issue is open and ready for the assignee to start work on it In Progress Active jira Edit This issue is being actively worked on at the moment by the assignee i Reopened Active jira Edit This issue was once resolved but the resolution was deemed incorrect From here issues are either marked assigned or resolved Resolved Active e jira Edit A resolution has been taken and it is awaiting verification by reporter From here issues are either reopened or are closed Closed Active jira Edit The issue is considered finished the resolution is correct Issues which are closed can be reopened c Incident Priority Click on the Priority hyperlink under Incident Standard Fields to bring up the Incident Priority mapping configuration screen To configure the data mappings for this field please fill in the external key values for the JiraDataSync plug in next to each Spiraleam value ield Value 1 Critical 2 High 3 Medium 4 Low The table lists each of the incident priorities available in SpiraTeam and provides you with the ability to enter the matching JIRA priority ID for each one You can
122. dbl6ggs lt value gt lt setting gt lt setting name EventLogSource serializeAs String gt lt value gt SpiraTeam Data Sync Service lt value gt lt setting gt lt setting name TraceLogging serializeAs String gt lt value gt False lt value gt lt setting gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt applicationSettings gt lt contiquration gt The sections that need to be verified and possibly changed are marked in yellow above You need to check the following information gt The polling interval allows you to specify how frequently the data synchronization service will ask Spiraleam and the external system for new data updates The value is specified in milliseconds and we recommend a value no smaller than 5 minutes i e 300 000ms The larger the number the longer it will take for data to be synchronized but the lower the network and server overhead gt The base URL to your instance SpiraTeam It is typically of the form http lt server name gt SpiraTeam Make sure that when you enter this URL on a browser on the server itself the application login page appears Do not include the Login aspx or any other page in this URL gt Avvalid login name and password to your instance of SpiraTeam This user needs to be a member of the project s that will be synchronized with Mantis and needs to have at least Incident create modify view permissions and Release create modify view permissions
123. downloads available for SpiraTeam http www inflectra com Spiraleam Downloads aspx Listed on this page will be the JIRA 5 x Plug In for Spiraleam Right click on this link and save the Zip compressed folder to the hard drive of the server where SpiraTeam is installed Note There are older plug ins for JIRA 3 x and JIRA 4 x that are described separately in Section 3 Open up the compressed folder and extract the JiraDataSync dll and Newtonsoft Json dil files and place them in the C Program Files Spiraleam Bin folder it may be SpiraTest or SpiraPlan depending on which product you re running This folder should already contain the DataSyncService exe and DataSyncService exe config files that are the primary files used for managing the data synchronization between Spiraleam and other systems If you do not have an on premise installation of SpiraTeam but instead are using a hosted subscription provided by Inflectra or a third party company you will not have access to the DataSyncService background service In such situations you should use the Desktop DataSync application instead This application is described in Appendix 1 and can be used instead of the server based DataSyncService 2 1 2 Configuring the Service To configure the integration service please open up the DataSyncService exe config file located in C Program Files SpiralTeam Bin with a text editor such as Notepad Once open it should look like lt xml version 1 0
124. ds sp Add Custom Field i Find More Custom Fields Field Configurations 7 d Name lype Available Context s Screens Field Configuration Custom Date Date Picker Issue type s Default Screen Global all issues Resolve Issue Screen Workflow Screen Free Text Field Free Text Field unlimited text Issue type s Default Screen This is a free text field Global all issues Multi Select Field Multi Select Issue type s Default Screen This is a multi select field Global all issues Single Select List Select List Issue type s Default Screen Single Select List Field Global all issues User Custom User Picker Issue type s Default Screen Global all issues Next for each of the Property Values in the table in the lower half of the page you need to enter the full name not the id this time of the custom field value as specified in JIRA Fields Custom Fields Configure Custom Field Multi Select Field Field Configurations Below are the Custom Field Configuration schemes for this custom field Schemes are applicable for various issues types in a particular context You can configure a custom field differently for Field Configuration each project context or in a global context Moreover project level schemes will over ride global ones Add new context View Custom Fields Default Configuration Scheme for Multi Select Field Default configuration scheme generated by JIRA Applicable contexts for sche
125. e external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name OnTime Sample Project External Key Test Project 1 Active If the project name does not match the name of the project you want to configure the data mapping for click on the Change Project hyperlink to change the current project To enable this project for data synchronization with OnTime you need to enter gt External Key This should be set to the name of the project token in OnTime Projects aaa Jefi ff more w Favorites All Projects Test Project 1 If you have a sub project you need to include both the parent and sub project names separated by a forward slash e g MyProject SubProject1 gt Active Flag Set this to Yes so that SpiraTeam knows that you want to synchronize data for this project Once the project has been completed setting the value to No will stop data synchronization reducing network utilization Click Update to confirm these settings Once you have enabled the project for data synchronization you can now enter the other data mapping values outlined below Note Once you have successfully configured the project when creating a new project you should choose the option to Create Project from Existing Project rather than Use Default Template so that all the project mappings
126. e fill in the JiraDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Component Custom Value Mapping Component 1 Yes 10001 Component 2 Yes 10010 Component 3 Yes 10020 First you need to enter the word Component as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Component field in Bugzilla Next for each of the Property Values in the table in the lower half of the page you need to enter the Bugzilla name of the various Components that are configured in Bugzilla b Bugzilla s Operating System Field If your instance of Bugzilla requires that all new issues are submitted with an Operating System then you will need to fill out this section You first need to create an incident custom property in SpiraTeam of type LIST that contains the various operating system names that exist inside Bugzilla Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the BugzillaDataSync external key values for
127. e need to configure the custom property mappings This is used to associate custom properties in SpiraTeam that map to custom fields in RTC From the View Edit Project Data Mapping screen you need to click on the name of the Incident Custom Property that you want to add data mapping information for We will consider the two different tyoes of mapping that you might want to enter Altifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Approved Archived Release Task a Text Custom Properties Click on the hyperlink of the text custom property under Incident Custom Properties to bring up the custom property mapping configuration screen For text custom properties there will be no values listed in the lower half of the screen Edit Custom Property Data Mapping Sample Application Two Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the RtcDataSyne external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Approved External Key osic_crn approved Custom Value Mapping You need to obtain the fully qualified XML name of the custom field in RTC that matches this custom property in SpiraT
128. e standard incident fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the ClearQuestDataSync plug in entry ClearQuestDatasync Project Data Mapping Sample Application Two Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the ClearQuestDataSyne plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization ta operate Project Name Sample Application Two External Key SAKAPL Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority Product Severity Resolution Status Release Task Priority Status From this screen you need to click on Priority Severity and Status in turn to configure their values a Incident Status Click on the Status hyperlink under Incident Standard Fields to bring up the Incident status mapping configuration screen Edit Standard Field Data Mapping Sample Application Two Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the ClearQuestDataSync plug in next to each Spiraleam value Assigned Assigned
129. e the project has been completed setting the value to No will stop data synchronization reducing network utilization Click Update to confirm these settings Once you have enabled the project for data synchronization you can now enter the other data mapping values outlined below Note Once you have successfully configured the project when creating a new project you should choose the option to Create Project from Existing Project rather than Use Default Template so that all the project mappings get copied across to the new project 4 2 2 Configuring the User Mapping To configure the mapping of users in the two systems you need to go to Administration gt Users gt View Edit Users which will bring up the list of users in the system Then click on the Edit button for a particular user that will be editing issues in Bugzilla Add Edit User Fred Bloggs Please review the information listed below and make any changes if necessary Once you have finished click Update Insert to confirm them First Name red Middle Initial Last Name loggs User Name edbloggs Email Address edbloggs mycompany com System Administrator Active User BugzillaData Sync ID edbloggs mycompany com JLDAP Managed User CI Change Password You will notice that below the Active flag for the user is a list of all the configured data synchronization plug ins In the text box next to the Bugzilla Data
130. eam as new comments In essence Spiraleam acts as a read only viewer of these incidents gt You are now able to perform test coverage and incident reporting inside Spiraleam using the test cases managed by SpiraTeam and the incidents managed on behalf of SpiraTeam inside Redmine 12 Using Spira with OnTime 11 This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with the OnTime 11 defect tracking system from AxoSoft The built in integration service allows the quality assurance team to manage their requirements and test cases in Spiraleam execute test runs in SpiraTest and then have the new incidents generated during the run be automatically loaded into OnTime Once the incidents are loaded into OnTime as defects the development team can then manage the lifecycle of these defects in OnTime and have the status changes in OnTime be reflected back in SpiraTeam Note This section refers to integrating with the older SOAP API that was available in AxoSoft OnTime 11 2010 This API was removed from AxoSoft OnTime in 2012 and we recommend you use the AxoSoft OnTime 14 Plugin instead that is described in section 10 above if you are using OnTime 14 or later 12 1 Configuring the Integration Service This section outlines how to configure the integration service to export incidents into OnTime and pick up subsequent status changes in OnTime and have them update SpiraTeam It
131. eam from the RTC documentation Once you have entered the name of the custom field click Update b List Custom Properties Click on the hyperlink of the list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen For list custom properties there will be a textbox for both the custom field itself and a mapping table for each of the custom property values that need to be mapped Edit Custom Property Data Mapping Sample Application Two Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the RtcDatasyne external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Hame Archived External Key ne _extarchived First you need to obtain the fully qualified XML name of the field in RTC that matches this custom property in SpiraTeam This should be entered in the External Key field below the name of the custom property Then you need enter the possible values in RTC for the custom property mapping each one to the corresponding SpiraTeam custom property value Once you have updated the various mapping sections you are now ready to start the service 9 3 Enabling the Data Synchronization 9 3 1 Starting the Service When SpiraTeam is installed a Windows Service SpiraTeam Data Sync Serv
132. ecret is a long hash that will be of the form For SpiraTeam 4 2 and earlier there is a limitation on the length of client secret that can be accepted so you need to break down the client secret into three parts of roughly equal length that you can enter into SpiraTeam For example we could have used e ykk8WD3eYfMJ6WbV1HtkutJv_w9jS2ah1ltSbwqs e 408Gp0_cPh5wTInjwfgPLN3 e _oCSHPVG5tpFkETHBgxUBKbXaTzzVqYtKC9_S 10 1 2 Download the OnTime Plug in Go to the Inflectra website and open up the page that lists the various downloads available for SpiraTeam http www inflectra com Spiraleam Downloads aspx Listed on this page will be the OnTime 14 Plug In for SpiraTeam Right click on this link and save the Zip compressed folder to the hard drive of the server where SpiraTeam is installed Open up the compressed folder and extract the following files and place them in the C Program Files SpiraTeam Bin folder it may be SpiraTest or SpiraPlan depending on which product you re running e AxosoftAPI NET dIl e OnTimeDataSync dll e Newtonsoft Json dll This folder should already contain the DataSyncService exe and DataSyncService exe config files that are the primary files used for managing the data synchronization between SpiraTeam and other systems If you do not have an on premise installation of SpiraTeam but instead are using a hosted subscription provided by Inflectra or a third party company you will not have access to the DataSy
133. ed over to Bugzilla they will get switched to the NEW status in Bugzilla which will then be synched back to Open in SpiraTeam That way you ll be able to see at a glance which incidents have been synched with Bugzilla and those that haven t b Incident Priority Click on the Priority hyperlink under Incident Standard Fields to bring up the Incident Priority mapping configuration screen Edit Standard Field Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the BugzillaData Sync plug in next to each Spiraleam value 1 Critical 2 High 3 Medium 4 Low Update j The table lists each of the incident priorities available in SpiraTeam and provides you with the ability to enter the matching Bugzilla priority for each one You can map multiple SpiraTeam fields to the same Bugzilla fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from Bugzilla gt SpiraTeam c Incident Severity Click on the Severity hyperlink under Incident Standard Fields to bring up the Incident severity mapping configuration screen Edit Standard Field Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in t
134. ed tatus concept F date 2 21 2010 Ha Address c AddE ditheleasekonsave treeView_HideAndRetres URL hiGeeeeelenl 222 1269366984030 date Hj 28 S Days Size 114367 bytes T Exclude weekends SS date 2 21 2010 3 Date M Release is active Protocol HyperT ext Transfer Protocol Created 3 23 2010 Modified 3 23 2010 biects ET All Projects O Product V Corporate Web Site Certificates All C Intranet Site _ Line of Business Apps 12 2 4 Configuring the Standard Field Mapping Now that the projects user and releases have been mapped correctly we need to configure the standard incident fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the OnTimeDataSync plug in entry OnTimeDataSync Project Data Mapping Sample OnTime Project Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the OnTimeData Sync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Sample OnTime Project Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority Replica
135. een Change Request Enhancement Incident Issue Limitation Risk Training The table lists each of the incident types available in SpiraTeam and provides you with the ability to enter the matching TFS work item type name for each one To make this easier we recommend that inside the Administration gt Edit Incident Statuses screen you first make all incident types inactive except Risk Issue and Bug since only those types make sense to synchronize with TFS b Incident Status Click on the Status hyperlink under Incident Standard Fields to bring up the Incident status mapping configuration screen Assigned ji Closed Tes Closed Fixed Duplicate res Closed Duplicate New Not Reproducible 5 Closed Cannot Reproduce Open Tes Active New Reopen res Active Not Fixed Resolved res Resolved Fixed The table lists each of the incident statuses available in SpiraTeam and provides you with the ability to enter the matching TFS work item State Reason for each one Since TFS uses separate State Active Resolved Closed and Reason Fixed Duplicate Not Fixed etc codes and SpiraTeam uses a single status code you need to concatenate the TFS State and Reason together with a plus sign so that the system knows that the incident status in SpiraTeam corresponds to that specific combination You can map multiple SpiraTeam fields to the same TFS fields e g New and Open in SpiraTeam are both equivalent to Active
136. el data mapping for each of the types of artifact that you will be synchronizing in this project Requirement Importance status Test Case Priority Incident Priority Custom Property 1 Severity Custom Property 2 Status z Release Task Priority Status We will consider the two different types of mapping that you might want to enter a Scalar Custom Properties This refers to custom properties that have a simple user entered value and don t need to have their specific options mapped between Spiraleam and Redmine All of the custom property types except List and Multi List fall into this category e g Text Date Boolean Decimal Integer etc Click on the hyperlink of the scalar custom property under Incident Custom Properties to bring up the custom property mapping configuration screen For scalar custom properties there will be no values listed in the lower half of the screen Edit Custom Property Data Mapping Redmine Demo Project Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the RedmineDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Custom Property 1 Custom Value Mapping You need to enter the ID of the custom field in Redmine that matches this custom property in SpiraTeam Once you have entered
137. eld Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project fh tt ee ual ey el e Ppt eee Gea a fa ese gee Bee aac vandari F elds LUSTtoOIT PTOpPenmies Incident Product Resolution Release Task Priority Status If the project name does not match the name of the project you want to configure the data mapping for click on the Change Project hyperlink to change the current project To enable this project for data synchronization with ClearQuest you need to enter gt External Key This should be set to the name of the project database in ClearQuest that will be mapped to the specific SpiraTeam project gt Active Flag Set this to Yes so that SpiraTeam knows that you want to synchronize data for this project Once the project has been completed setting the value to No will stop data synchronization reducing network utilization Click Update to confirm these settings Once you have enabled the project for data synchronization you can now enter the other data mapping values outlined below Note Once you have successfully configured the project when creating a new project you should choose the option to Create Project from Existing Project rather than Use Default Template so that all the project mappings get copied across to the new project 8 2 2 Configuring the User M
138. em Connection Info this should the full URL to the OnTime SDK This is typically something like http lt OnTime server name gt OnTimeSdk You may need to check in the IIS Management Console of the OnTime server to verify the virtual directory name Login this should be set to the GUID that you specified in the Web Config file in step 2 1 1 above Password this should be left blank as it s not used by the OnTime data sync plug in Time Offset normally this should be set to zero but if you find that defects being changed in OnTime are not being updated in SpiraTeam try increasing the value as this will tell the data synchronization plug in to add on the time offset in hours when comparing date time stamps Also if your OnTime installation is running on a server set to a different time zone then you should add in the number of hours difference between the servers time zones here Auto Map Users this is not currently used by the OnTime data sync plug in and can be ignored Custom 01 05 these are not currently used by the OnTime data sync plug in and can be left blank 12 2 Configuring the Data Mapping Next you need to configure the data mapping between SpiraTeam and OnTime This allows the various projects users releases incident statuses priorities severities and custom property values used in the two applications to be related to each other This is important as without a correct mapping th
139. ems please navigate to Planning gt Releases and click on the Release Iteration in question Make sure you have the Overview tab visible and expand the Details section of the release iteration Release 3 0 0 1 New Release RL 000024 Name Root Release Overview Incidents Reqs amp Tasks Test Cases Test Runs Attachments History v Details ill Version 1 000 Creator System Administrator v Start End Date l s203 10 8 2013 Creation Date 6 5 2013 6 07 56 PM C Resources 1 Active Yes Non Working 0o person days Iteration No v Plan Effort 176 00 Available Effort 176 00 In addition to the standard fields and custom properties configured for Releases you will see an additional text property called OnTimeDataSync ID that is used to store the mapped external identifier for the equivalent Version in OnTime You need to locate the ID of the equivalent version in OnTime enter it into this text box and click Save You should now repeat for all the other pre existing releases Note The OnTime ID can be found by looking at the URL inside OnTime when choosing to Edit the release in question The URL will include the section Releaseld X where X is the numeric ID of the version inside OnTime Properties General OnTime Web Edition otes ame Corporate Web ste gt lease Root Release z Type HTML Document nes Podua HE Connection Not Encrypt
140. encoding utf 8 gt lt conitiguration gt lt configSections gt lt sectionGroup name applicationSettings type System Configuration ApplicationSettingsGroup System Version 2 0 0 0 Culture neutral PublicKeyToken b77a5c561934e089 gt lt section name Inflectra SpiraTest DataSyncService Properties Settings type System Configuration ClientSettingsSection System Version 2 0 0 0 Culture neutral PublickeyToken b77a5c561934e089 requirePermission false gt lt sectionGroup gt lt configSections gt lt applicationSettings gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt setting name PollingInterval serializeAs String gt lt value gt 600000 lt value gt lt setting gt lt setting name WebServiceUrl serializeAs String gt lt value gt http localhost SpiraTeam lt value gt lt setting gt lt setting name Login serializeAs String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name Password serializeAs String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name EventLogSource serializeAs String gt lt value gt SpiraTeam Data Sync Service lt value gt lt setting gt lt setting name TraceLogging serializeAs String gt lt value gt False lt value gt lt setting gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt applicationSettings gt lt configuration gt The sections that need to be
141. ent artifact type called Area and link it to the Area custom list you created in the previous step This will now be available for mapping Now back in the data mapping page click on the Area hyperlink under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping TFS Test Project 1 Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the MsTisDataSync extemal key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Area Custom Value Mapping Administration Customization Management Reporting First you need to enter the word Area as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Area field in TFS Next for each of the Property Values in the table in the lower half of the page you need to enter the ID of the various Areas that are configured in TFS The TFS Area ID is not visible in the TFS user interface but can instead be located by opening up the SQL Server that it s installed on opening the TfsWorkltem Tracking database in TFS 2010 and later it will named after your project collection instead and locating the TreeNodes table TypelD 44 44
142. ere is no way for the integration service to know that an Open incident in SpiraTeam is the same as an Open defect in OnTime for example The following mapping information needs to be setup in SpiraTeam gt The mapping of the project identifiers for the projects that need to be synchronized gt The mapping of users in the system gt The mapping of releases in the system gt The mapping of the various standard fields in the system gt The mapping of the various custom properties in the system Each of these is explained in turn below 12 2 1 Configuring the Project Mapping From the data synchronization administration page you need to click on the View Project Mappings hyperlink next to the OnTime plug in name This will take you to the data mapping home page for the currently selected project OnTimeDataSync Project Data Mapping Sample OnTime Project Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the OnTimeDataSync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Sample OnTime Project Artifact Field Mapping Please click on each of the links below to configure the fleld level data mapping for each of the types of artifact that you will be synchronizing in this proje
143. eric ID of the Custom Field inside JIRA Next for each of the Property Values in the table in the lower half of the page you need to enter the full name not the id this time of the custom field value as specified in JIRA c JIRA s Component Field If your instance of JIRA requires that all new issues are submitted with a Component then you will need to fill out this section You first need to create an incident custom property in SpiraTeam of type LIST that contains the various component names that exist inside JIRA Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Component a Custom Value Mapping Component 1 Yes 40001 Component 2 Yes 40010 Component 3 Yes 40020 First you need to enter the word Component as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Component field in JIRA Next for each of the Property Values in the ta
144. ersion in Bugzilla enter it into this text box and click Save You should now repeat for all the other releases and iterations in the project If you are using the plugin for Bugzilla 4 x then any Versions that have already been created in Bugzilla will be automatically imported into SpiraTeam if they do not already exist in SpiraTeam and they have not already been mapped 4 2 4 Configuring the Standard Field Mapping Now that the projects user and releases have been mapped correctly we need to configure the standard incident fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the BugzillaDataSync plug in entry View Edit Project Data Mapping Library Information System Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the BugzillaDataSync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need ta be mapped for the synchronization to operate Project Name Library Information System External Key deleteable Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority Resolution Severity Notes Status Component yp Operating System Hardware Re
145. es Support inflectra com who will help you troubleshoot the problem To use SpiraTeam with ClearQuest on an ongoing basis we recommend the following general processes be followed gt When running tests in SpiraTest or SpiraTeam defects found should be logged through the Test Execution Wizard as normal gt Developers using ClearQuest can log new defects into either SpiraTeam or ClearQuest In either case they will get loaded into the other system gt Once created in one of the systems and successfully replicated to the other system the incident should not be modified again inside SpiraTeam gt At this point the incident should not be acted upon inside SpiraTeam and all data changes to the issue should be made inside ClearQuest To enforce this you should modify the workflows set up in SpiraTeam so that the various fields are marked as inactive for all the incident statuses other than the New status This will allow someone to submit an incident in SpiraTeam but will prevent them making changes in conflict with ClearQuest after that point gt As the issue progresses through the customized ClearQuest workflow changes to the type of issue changes to Its status priority description and resolution will be updated automatically in Spiraleam In essence SpiraTeam acts as a read only viewer of these incidents gt You are now able to perform test coverage and incident reporting inside SpiraTest SpiraTeam using the test
146. es a user to configure and schedule au Local Systerh Sy TCP IP NetBIOS Helper Enables support For NetBIOS over TCP IP N Local Service Siy Telephony Provides Telephony API TAPI support For p Local Systeri os Talan Cackin w a cmeneke seme ha hee am ba biie eee lasal Cbam extended Standard Click on the SpiraTeam Data Sync Service entry and click on the link to start the service Then right click the service entry and choose the option to set the startup type to Automatic This will ensure that synchronization continues between SpiraTeam and OnTime after a reboot of the server 12 3 2 Using SpiraTeam with OnTime Now that the integration service has been configured and the service started initially any incidents created in SpiraTeam for the specified projects will be imported into OnTime At this point we recommend opening the Windows Event Viewer and choosing the Application Log In this log any error messages raised by the SpiraTeam Data Sync Service will be displayed If you see any error messages at this point we recommend immediately stopping the SpiraTeam service and checking the various mapping entries If you cannot see any defects with the mapping information we recommend sending a copy of the event log message s to Inflectra customer services Support inflectra com who will help you troubleshoot the problem To use SpiraTeam with OnTime on an ongoing basis we recommend the following general pr
147. existing releases Note The JIRA ID can be found by looking at the URL inside JIRA when choosing to View Edit the version name description The URL will include the section id X where X is the numeric ID of the version inside JIRA 3 2 4 Configuring the Standard Field Mapping Now that the projects user and releases have been mapped correctly we need to configure the standard incident fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the JiraDataSync plug in entry View Edit Project Data Mapping Library Information System Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the JiraData Sync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Library Information System Active Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority Notes Severity Operating System Status Type Release Notes Operating System Task Priority Status From this screen you need to click on Priority Severity Status and Type in turn to configure their values a Incident Type Click
148. ext in the SpiraTeam field does not match an available item in the lists then Mantis may leave the field blank or set it to the default value a Mapping custom fields For a Spiraleam test field all you need to do is link the custom field to the custom field in Mantis To do this click on the name of the custom field under the Custom Properties header in the MantisDataSync Project Mappings and you will see a screen allowing you to enter the External Key insert screenshot of custom map text prop screen with mapping for below In the External Key field put the name of your custom field in Mantis Edit custom field Type List hi Possible Values Windows Linux Mac Default Value Windows Once you have updated the various mapping sections you are now ready to start the service 7 3 Enabling the Data Synchronization 7 3 1 Starting the Service When SpiraTeam is installed a Windows Service SpiraTeam Data Sync Service is installed along with the web application However to avoid wasting system resources this service is initially set to run manually To ensure continued synchronization of SpiraTeam with Mantis we recommend starting the service and setting its startup type to Automatic Delayed or Automatic To make these changes open up the Windows Control Panel click on the Administrative Tools link and then choose the Services option This will bring up the Windows Service control panel n
149. f If you are using a Window Live ID just leave this field blank gt Custom 02 This field should contain a comma separated list of work item types that you want to synchronize as Spirateam Tasks as opposed to Incidents Normally you would want to list at least the TFS Task work item type in this field gt Custom 03 If you would like the system to display the SpiraTeam artifact ID e g IN5 for incidents or TK36 for tasks in a custom field inside TFS you should just enter the name of the appropriate TFS field from your process template e g Soira IncidentId and then when the incident or task is added to TFS the corresponding SpiraTeam ID will be added to that field of the work item gt Custom 04 Depending on your TFS process template the data synchronization plugin may not be allowed to set the detector of the incident inside TFS If you would like the system to display the detector of the incident as recorded in SpiraTeam in a custom field inside TFS you should just enter the name of the appropriate TFS field from your process template e g Spira Detector and then when the incident is added to TFS the corresponding detector s name will be added to that field of the work item Custom 05 This field should contain a comma separated list of work item types that you want to synchronize as Spiraleam Requirements as opposed to Incidents Normally you would want to list at least the TFS User Story work item type
150. f your instance of JIRA requires that all new issues are submitted with a Security Level then you will need to fill out this section You first need to create an incident custom property in SpiraTeam of type LIST that contains the various security levels that exist inside JIRA Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen First you need to enter the word SecurityLevel as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Security Level field in JIRA Next for each of the Property Values in the table in the lower half of the page you need to enter the JIRA ID of the various Security Levels that are configured in JIRA The external ID can be found by looking at the URL inside JIRA which choosing to View Edit the security level name description g JIRA s Issue Key Field JIRA 4 x Plug In Only It can be convenient to create a SpiraTeam custom property to store the JIRA Issue Key the ID used to identify an issue in JIRA This allows you to display a list of incients in SpiraTest and see the corresponding JIRA ID in the same list You first need to create an incident custom property in SpiraTeam of type TEXT that will be used to store the JIRA issue key within SpiraTeam Then click on the hyperlink of this new list custom proper
151. fects with the mapping information we recommend sending a copy of the event log message s to Inflectra customer services Support inflectra com who will help you troubleshoot the problem To use SpiraTeam with OnTime on an ongoing basis we recommend the following general processes be followed gt When running tests in SpiraTeam defects found should be logged through the Add Incident option as normal gt Developers can log new defects into either SpiraTeam or OnTime In either case they will get loaded into the other system gt Once created in one of the systems and successfully replicated to the other system the incident should not be modified again inside SpiraTeam gt At this point the incident should not be acted upon inside SpiraTeam and all data changes to the defect should be made inside OnTime To enforce this you can modify the workflows set up in SpiraTeam so that the various fields are marked as inactive for all the incident statuses other than the New status This will allow someone to submit an incident in SpiraTeam but will prevent them making changes in conflict with OnTime after that point gt As the defect progresses through the OnTime workflow changes to the status priority severity and resolution will be updated automatically in SpiraTeam In essence SpiraTeam acts as a read only viewer of these incidents gt You are now able to perform test coverage and incident reporting inside Spi
152. figuring the Integration Service This section outlines how to configure the integration service to export incidents into FogBugz and pick up new cases and changes to existing cases in FogBugz and have them update SpiraTeam It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam v2 2 or later and a working installation of FogBugz v6 1 or later If you have an earlier version of SpiraTeam you will need to upgrade to at least v2 2 before trying to integrate with FogBugz The steps that need to be performed to configure integration with FogBugz are as follows Download the latest FogBugz Data Sync plug in for SpiraTeam from our website Vv Setup the plug in in SpiraTeam to point to the correct instance of FogBugz gt Configure the data field mappings between SpiraTeam and FogBugz gt Start the service and verify data transfer 6 1 1 Download the FogBugz Plug In Go to the Inflectra website and open up the page that lists the various downloads available for SpiraTeam http www inflectra com Spiraleam Downloads aspx Listed on this page will be the FogBugz Plug In for SpiraTeam Right click on this link and save the Zip compressed folder to the hard drive of the server where SpiraTeam is installed Open up the compressed folder and extract the FogBugzDataSync dll file and place it in the C Program Files SpiraTeam Bin folder it may be SpiraTest or SpiraPlan depending on which product you re running Th
153. g general processes be followed gt When running tests in SpiraTest or SpiraTeam defects found should be logged through the Test Execution Wizard as normal gt Developers can log new defects into either SpiraTeam or JIRA In either case they will get loaded into the other system gt Once created in one of the systems and successfully replicated to the other system the incident should not be modified again inside SpiraTeam gt At this point the incident should not be acted upon inside SpiraTeam and all data changes to the issue should be made inside JIRA To enforce this you should modify the workflows set up in SpiraTeam so that the various fields are marked as inactive for all the incident statuses other than the New status This will allow someone to submit an incident in SpiraTeam but will prevent them making changes in conflict with JIRA after that point As the issue progresses through the customized JIRA workflow changes to the type of issue changes to its status priority description and resolution will be updated automatically in Spiraleam In essence SpiraTeam acts as a read only viewer of these incidents You are now able to perform test coverage and incident reporting inside SpiraTest SpiraTeam using the test cases managed by SpiraTest Spiraleam and the incidents managed on behalf of Spiral est SpiraTeam inside JIRA 3 Using SpiraTeam with JIRA 3 4 This section outlines how to use SpiraTest Spira
154. g ins If you already see an entry for ClearQuestDataSync you should click on its Edit link If you don t see such an entry in the list please click on the Add button instead In either case you will be taken to the following screen where you can enter or modify the ClearQuest Data Synchronization plug in Edit Plug In ClearQuestDatasyne lt lt Back to Data synchronization Home Please enterfedit the following information for the plug in The exact information that needs to be entered is specific ta each plug in and you should refer to the documentation for the plug in when entering changing it Name ClearQuestDataSync Description This plug in allows incidents in the system to be synchronized with the Clearliuest defect tracking system Connection Info Login Password Time Offset Cl Auto Map Users You need to fill out the following fields for the ClearQuest Plug in to operate correctly gt Name this needs to be set to ClearQuestDataSync This needs to match the name of the plug in DLL assembly that was copied into the C Program Files SpiraTeam Bin folder minus the dll file extension If you renamed the ClearQuestDataSync dll file for any reason then you need to change the name here to match gt Description this should be set to a description of the plug in This is an optional field that is used for documentation purposes and is not actually used by the system gt Connection Info this
155. get copied across to the new project 10 2 2 Configuring the User Mapping This section can be skipped if you enabled the AutoMap Users option earlier To configure the mapping of users in the two systems you need to go to Administration gt Users gt View Edit Users which will bring up the list of users in the system Then click on the Edit button for a particular user that will be editing defects in OnTime Add Edit User System Administrator Please review the information listed below and make any changes if necessary Once you have finished click Update Insert to confirm them First Name System Middle Initial Last Name Administrator O E Project Membership Passwords amp Security Data Mapping Tara V ault Membership OnTimeDataSync ID You will notice that in the Data Mapping tab for the user is a list of all the configured data synchronization plug ins In the text box next to the OnTime Data Sync plug in you need to enter the Login Name for this username in OnTime This will allow the data synchronization plug in to know which user in SpiraTeam match which equivalent user in OnTime Click Update once you ve entered the appropriate login name You should now repeat for the other users who will be active in both systems 10 2 3 Configuring the Release Mapping When the data synchronization service runs when it comes across a release iteration in SpiraTeam that it has
156. go to Administration gt Users gt View Edit Users which will bring up the list of users in the system Then click on the Edit button for a particular user that will be editing issues in JIRA Add Edit User Fred Bloggs Please review the information listed below and make any changes if necessary Once you have finished click Update Insert to confirm them First Name red Middle Initial Last Name loggs User Name edbloggs Email Address edbloggs mycompany com System Administrator Active User BugzillaData Sync ID FogBugzData Sync ID JiraData Sync ID MsTfsData Sync ID You will notice that below the Active flag for the user is a list of all the configured data synchronization plug ins In the text box next to the JIRA Data Sync plug in you need to enter the login for this username in JIRA This will allow the data synchronization plug in to Know which user in SpiraTeam match which equivalent user in JIRA Click Update once you ve entered the appropriate login name You should now repeat for the other users who will be active in both systems 3 2 3 Configuring the Release Mapping When the data synchronization service runs when it comes across a release iteration in SpiraTeam that it has not seen before it will create a corresponding Version in JIRA Similarly if it comes across a new Version in JIRA that it has not seen before it will create a new Release in SpiraTeam Therefore when using b
157. he event log message s to Inflectra customer services Support inflectra com who will help you troubleshoot the problem To use SpiraTeam with FogBugz on an ongoing basis we recommend the following general processes be followed gt When running tests in SpiraTest or SpiraTeam defects found should be logged through the Test Execution Wizard as normal gt Developers using FogBugz can log new defects into either SpiraTeam or FogBugz In either case they will get loaded into the other system gt Once created in one of the systems and successfully replicated to the other system the incident should not be modified again inside SpiraTeam Since FogBugz is considered the master system for incidents cases all data changes to the case should be made inside FogBugz To enforce this you should modify the workflows set up in SpiraTeam so that the various fields are marked as inactive for all the incident statuses other than the New status This will allow someone to submit an incident in SpiraTeam but will prevent them making changes in conflict with FogBugz after that point gt As the case progresses through the FogBugz workflow changes to the type of case changes to its status priority description and resolution will be updated automatically in SpiraTeam In essence SpiraTeam acts as a read only viewer of these incidents gt You are now able to perform test coverage and incident reporting inside SpiraTest SpiraTeam using t
158. he external key values for the BugzillaDataSync plug in next to each Spiraleam value 1 Critical re critical 2 High major 3 Medium fer anu 4 Low Pes minor The table lists each of the incident severities available in SpiraTeam and provides you with the ability to enter the matching Bugzilla severity for each one You can map multiple SpiraTeam fields to the same Bugzilla fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from Bugzilla gt SpiraTeam 4 2 5 Configuring the Custom Property Mapping Now that the various SpiraTeam standard fields have been mapped correctly we need to configure the custom property mappings This is used for custom properties in SpiraTeam that are used to map to standard fields in Bugzilla Component Hardware Operating System and Resolution that don t exist in Spiraleam You need to make sure that you have first added custom lists in SpiraTeam that contain the list of Components Hardware platforms and Operating Systems used in Bugzilla and that you have setup those lists as Custom Properties on the Incident artifact type Once that s done from the View Edit Project Data Mapping screen you need to click on the name of the Incident Custom Property that you want to add data mapping information for We will consider the four different types of mapping that you might want to enter in turn View
159. he full URL to OnTime This is typically something like httos mysite axosoft com Login this should be set to the login that you use to access OnTime through its web interface Password this should be set to the password that you use to access OnTime through its web interface Time Offset normally this should be set to zero but if you find that defects being changed in OnTime are not being updated in SpiraTeam try increasing the value as this will tell the data synchronization plug in to add on the time offset in hours when comparing date time stamps Auto Map Users This changes the way that the plugin maps users in SpiraTeam to those in OnTime gt Auto Map True With this setting all users in SpiraTeam need to have the same username as those in OnTime If this is the case then you do not need to perform the user mapping task outlined in section 10 2 2 This is a big time saver if you can guarantee that all usernames are the same in both systems gt Auto Map False With this setting users in SpiraTeam and OnTime are free to have different usernames because you specify the corresponding OnTime login for each user as outlined in section 10 2 2 Custom 01 This should contain the Client ID value from the OnTime API Key screen Custom 02 04 This should contain the three segments of the OnTime Client Secret that you obtained from the OnTime API Key Screen Custom 05 this is not currently used by the OnTime data
160. he project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Sample OnTime Project Active Artifact Field Mapping Please click on each of the links below to configure the fleld level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority ReplicationProcedures Severity OnTime Operating System Status OnTime Environment Type Release Task Priority Status a Text Custom Properties Click on the hyperlink of the text custom property under Incident Custom Properties to bring up the custom property mapping configuration screen For text custom properties there will be no values listed in the lower half of the screen Edit Custom Property Data Mapping Sample OnTime Project Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the OnTimeDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Notes ExtenelKey You need to lookup the display name of the custom field in OnTime that matches this custom property in SpiraTeam Once you have entered the id of the custom field click Update b List Custom Properties Click on the hyperlink of the li
161. he reverse synchronization from FogBugz gt SpiraTeam Since both applications allow you to customize the priority list we recommend that you modify the list in both systems to be the same and then map them one to one as this will be easier for users to understand In the example above we have switched over SpiraTeam to match the priorities in FogBugz but you could do it the other way around as well The FogBugz Priority IDs can be found by going to Settings gt Priorities and viewing the priorities Priority You can edit the text associated with each priority entry Priority Number Priority Label The priority ID is the priority number value displayed in the left hand column 6 2 5 Configuring the Custom Property Mapping Now that the various SpiraTeam standard fields have been mapped correctly we need to configure the custom property mappings This is used for custom properties in SpiraTeam that are used to map to standard fields in FogBugz Computer Version and Area that don t exist in SpiraTeam From the View Edit Project Data Mapping screen you need to click on the name of the Incident Custom Property that you want to add data mapping information for We will consider the three different types of mapping that you typically will want to enter Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing
162. he test cases managed by SpiraTest Spiraleam and the incidents managed on behalf of SpiraTest SpiraTeam inside FogBugz 7 Using SpiraTeam with Mantis This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with the Mantis issue tracking system The built in integration service allows the quality assurance team to manage their requirements and test cases in SpiraTeam execute test runs in Spiralest and then have the new incidents generated during the run be automatically loaded into Mantis Once the incidents are synchronized into Mantis the development team can then manage the issues in Mantis and have the status changes and additional notes entered in Mantis be reflected back in SpiralTeam In addition any new issues logged into mantis will get imported into SpiraTeam so that they can be linked to test cases and requirements 7 1 Configuring the Integration Service This section outlines how to configure the Data Sync service to export incidents into Mantis and pick up new issues and changes to existing issues in Mantis and have them update SpiraTeam It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam v2 3 or later and a working installation of Mantis v1 1 8 or later If you have an earlier version of SpiraTeam you will need to upgrade to at least v2 3 before trying to integrate with Mantis If you have an earlier version of Mantis you w
163. his will now be available for mapping Now back in the data mapping page click on the Area hyperlink under Task Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping TFS Test Project 1 Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the MsTisDataSync extemal key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Area Custom Value Mapping Administration Customization Management Reporting First you need to enter the word Area as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Area field in TFS Next for each of the Property Values in the table in the lower half of the page you need to enter the ID of the various Areas that are configured in TFS The TFS Area ID is not visible in the TFS user interface but can instead be located by opening up the SQL Server that it s installed on opening the TfsWorkltem Tracking database in TFS 2010 and later it will named after your project collection instead and locating the IreeNodes table Once you have found the matching Area by name the numeric value stored in the ID column the one on the left is the value th
164. hoose the option to Create Project from Existing Project rather than Use Default Template so that all the project mappings get copied across to the new project 2 2 2 Configuring the User Mapping To configure the mapping of users in the two systems you need to go to Administration gt Users gt View Edit Users which will bring up the list of users in the system Then click on the Edit button for a particular user that will be editing issues in JIRA Add Edit User Fred Bloggs Please review the information listed below and make any changes if necessary Once you have finished click Update Insert to confirm them First Name red Middle Initial Last Name loggs User Name fredbloggs Department A Email Address Email Enabled System Administrator Active Locked Out RSS Token Enable RSS Feeds Project Membership Passwords amp Security Data Mapping JiraData Sync ID fredbloggs Click on the Data Mapping tab to list all the configured data synchronization plug ins for this user In the text box next to the JIRA Data Sync plug in you need to enter the login for this username in JIRA This will allow the data synchronization plug in to know which user in SpiraTeam match which equivalent user in JIRA Click Update once you ve entered the appropriate login name You should now repeat for the other users who will be active in both systems If you have set the Auto M
165. hronization plug ins If you already see an entry for OnTimeDataSync you should click on its Edit link If you don t see such an entry in the list please click on the Add button instead In either case you will be taken to the following screen where you can enter or modify the OnTime Data Synchronization plug in Edit Plug In OnTimeDataSync lt lt Back to Data Synchronization Home Please enter edit the following information for the plug in The exact information that needs to be entered is specific to e Name ach plug in and you should refer to the documentation for the plug in when entering changing it OnTimeDataSync Description Connection Info http inflectrasvr04 OnTimeSdk Login Password 66ACD352 16C0 4485 6498 8C46 Time Offset C Auto Map Users Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 You need to fill out the following fields for the OnTime Plug in to operate correctly gt Name this needs to be set to OnTimeDataSync This needs to match the name of the plug in DLL assembly that was copied into the C Program Files SpiraTeam Bin folder minus the dll file extension If you renamed the OnTimeDataSync dll file for any reason then you need to change the name here to match Description this should be set to a description of the plug in This is an optional field that is used for documentation purposes and is not actually used by the syst
166. hronized The filter uses the following syntax Property Value Property Value For example to limit the incidents to only have those where List01 5 and Text08 Hello and Text05 is not blank you would use List01 5 Text08 Hello Text05 gt Custom 03 ClearQuest doesn t have a built in Detected in Release field If you would like to map a custom ClearQuest field to the SpiraTeam Detected in Release simply enter in the name of the ClearQuest field here gt Custom 04 ClearQuest doesn t have a built in Resolved in Release field If you would like to map a custom ClearQuest field to the SpiraTeam Resolved in Release simply enter in the name of the ClearQuest field here gt Custom 05 This is the optional DBset value when you have installations with more than one database set If you have a single database set you can just leave this blank If you enter a field name in either Custom 03 or Custom 04 you will need to also map the various releases in SpiraTeam to their corresponding equivalent field value in ClearQuest To do that click on Planning gt Releases and choose a specific release Then in the ClearQuest DataSync ID field under the Custom Properties tab you need to enter the name of the equivalent ClearQuest release 8 2 Configuring the Data Mapping Next you need to configure the data mapping between SpiraTeam and ClearQuest This allows the various projects users incident
167. icates get created when you first enable the data synchronization service Therefore for any Releases Iterations that already exist in BOTH systems please navigate to Planning gt Releases and click on the Release Iteration in question Make sure you have the Overview tab visible and expand the Details section of the release iteration Iteration 3 1 0 0 Iteration 3 1 RL 000021 Name Iteration 3 1 Overview Incidents Regs amp Tasks Test Cases Test Runs Attachments History LY Details i o Version 3 1 0 0 Creator System Administrator Start End Date 6 5 2013 es f 71512013 Creation Date 6 5 2013 5 55 00 PM Resources 1 Active Yes v Non Working 0 person days Iteration Yes v Plan Effort Available Effort 184 00 MsTfsDataSync ID g x In addition to the standard fields and custom properties configured for Releases you will see an additional text property called MsTfsDataSync ID that is used to store the mapped external identifier for the equivalent Version in TFS You need to locate the ID of the equivalent Iteration in TFS enter it into this text box and click Save You should now repeat for all the other pre existing releases The TFS Iteration ID is not visible in the TFS user interface but can instead be located by opening up the SQL Server that it s installed on opening the TfsWo
168. ice is installed along with the web application However to avoid wasting system resources this service is initially set to run manually To ensure continued synchronization of SpiraTeam with RTC we recommend starting the service and setting its startup type to Automatic To make these changes open up the Windows Control Panel click on the Administrative Tools link and then choose the Services option This will bring up the Windows Service control panel niu Services Fle Action View Help Beoe AM gt Gy Services Local i Services Local SpiraTeam Data Sync Service Start the service Description Manages the data synchronization between SpiraTeam and other external systems Name Sy Secunty Accounts Manager By Security Center egy Server Sa Shell Hardware Detection Sia Simple Mail Transfer Protocol SMTP By Smart Card th SpiraTeam Data Syne Service By SQLAgentsSPIRA Sy SOLSERVERAGENT By SSOP Discovery Service Siy System Event Notification By System Restore Service Description Stores security information For local user acc Monitors system security settings and config Supports File print and named pipe sharing Provides notifications For AutoPlay hardware Transports etachronic mail across the network Manages access to smart cards read by this Enables cescovery of UPn devices on your h Tracks system events such as Windows laga Performs system restore functions To
169. ick Update Note The ID can be found by looking at the URL inside JIRA when choosing to View Edit the Custom Field The URL will include the section id X where X is the numeric ID of the Custom Field inside JIRA b List Custom Properties Click on the hyperlink of the list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen For list custom properties there will be a textbox for both the custom field itself and a mapping table for each of the custom property values that need to be mapped Edit Custom Property Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Operating System External Key 49990 Custom Value Mapping Property Value Windows 2000 Windows 2003 Windows NT 4 0 fo Windows Vista Windows XP First you need to lookup the ID of the custom field in JIRA that matches this custom property in Spiraleam This should be entered in the External Key field below the name of the custom property Note The ID can be found by looking at the URL inside JIRA when choosing to View Edit the Custom Field The URL will include the section id X where X is the num
170. ill need to upgrade it to at least v1 1 8 or the Data Sync will report an error The steps that need to be performed to configure integration with Mantis are as follows Download the latest Mantis Data Sync plug in for SpiraTeam from our website Vv Setup the plug in in SpiraTeam to point to the correct instance of Mantis gt Configure the data field mappings between Spiraleam and Mantis gt Start the service and verify data transfer 7 1 1 Download the Mantis Plug In Go to the Inflectra website and open up the page that lists the various downloads available for SpiraTeam http www inflectra com Spiraleam Downloads aspx Listed on this page will be the Mantis Plug In for Spiraleam Right click on this link and save the Zip compressed folder to the hard drive of the server where SpiraTeam is installed Open up the compressed folder and extract the MantisDataSync dll file and place it in the C Program Files SpiraTeam Bin folder it may be SpiraTest or SpiraPlan depending on which product you re running This folder should already contain the DataSyncService exe and DataSyncService exe config files that are the primary files used for managing the data synchronization between SpiraTeam and other systems If you do not have an on premise installation of SpiraTeam but instead are using a hosted subscription provided by Inflectra or a third party company you will not have access to the DataSyncService background service In such situat
171. in these projects Once you have made these changes save the file and proceed to the next stage 7 1 3 Configuring the Plug In The next step is to configure the plug in within SpiraTeam so that the system knows how to access the Mantis server To start the configuration open up SpiraTeam in a web browser log in using a valid account that has System Administration level privileges and click on the System gt Data Synchronization administration option from the left hand navigation Data Synchronization Refresh Spiraleam is able to communicate with a variety of external systems and applications using its background data synchronization service and library of available plug ins This page allows you to view add and modify the list of plug ins make changes to their configuration and verify the status of the most recent synchronization In addition you can force a particular plug in to perform a complete data synchronization by resetting its date of last sync MantisDataSync Data Mapping gt View Project Mappings This screen lists all the plug ins already configured in the system Depending on whether you chose the option to include sample data in your installation or not you will see either an empty screen or a list of sample data synchronization plug ins If you already see an entry for MantisDataSync you should click on its Edit link If you don t see such an entry in the list please click on the Add
172. inside Mantis 8 Using SpiraTeam with ClearQuest This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with the ClearQuest defect tracking system The built in integration service allows the quality assurance team to manage their requirements and test cases in SpiraTeam execute test runs in Spiralest and then have the new incidents generated during the run be automatically loaded into ClearQuest Once the incidents are loaded into ClearQuest as defects the development team can then manage the lifecycle of these defects in ClearQuest and have the status changes in ClearQuest be reflected back in SpiraTeam In addition any issues logged directly into ClearQuest will get imported into Spiraleam so that they can be linked to test cases and requirements 8 1 Configuring the Integration Service This section outlines how to configure the integration service to export incidents into ClearQuest and pick up subsequent status changes in ClearQuest and have them be updated in SpiraTeam It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam v3 0 or higher and a working installation of IBM Rational ClearQuest 7 0 or higher If you have an earlier version of SpiraTeam you will need to upgrade to at least v3 0 before trying to integrate with ClearQuest The steps that need to be performed to configure integration with ClearQuest are as follows
173. inside TFS you should just enter the name of the appropriate TFS field from your process template e g Spira Detector and then when the incident is added to TFS the corresponding detector s name will be added to that field of the work item Custom 05 this is not used by this version of the plugin and can be ignored c TFS 2005 2008 Plugin Please fill out the fields as follows gt gt VV v Auto Map Users this is not used by this version of the plugin and can be ignored Custom 01 This is used to specify the Windows Active Directory Domain that the Windows user specified above is a member of If you are running TFS on a Windows workgroup just use the server name and make sure that the Windows user above is a user on that server itself Custom 02 This is used to specify if you want to synchronize Incidents Tasks or Both By default this field is blank meaning synchronize both types of artifact However if you enter in Incidents into this field it will tell the system to only synchronize incidents and if you enter Tasks it will tell the system to only synchronize tasks Custom 03 this is not used by this version of the plugin and can be ignored Custom 04 this is not used by this version of the plugin and can be ignored Custom 05 this is not used by this version of the plugin and can be ignored 5 2 Configuring the Data Mapping Next you need to configure the data mapping between Spir
174. ions you should use the Desktop DataSync application instead This application is described in Appendix 1 and can be used instead of the server based DataSyncService 7 1 2 Configuring the Service To configure the integration service please open up the DataSyncService exe config file located in C Program Files Spiraleam Bin with a text editor such as Notepad Once open it should look like lt xml version 1 0 encoding utf 8 gt lt CONLLOUraLLOn gt CONTIGSeCt10nSs gt lt sectionGroup name applicationSettings type System Configuration ApplicationSettingsGroup System Version 2 0 0 0 Culture neutral PublicKeyToken b77a5c561934e089 gt lt section name Inflectra SpiraTest DataSyncService Properties Settings type System Configuration ClientSettingsSection System Version 2 0 0 0 Culture neutral PublickeyToken b77a5c561934e089 requirePermission false gt lt sectionGroup gt lt configSections gt lt applicationSettings gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt setting name PollingInterval serializeAs String gt lt value gt 600000 lt value gt lt setting gt lt setting name WebServiceUrl serializeAs String gt lt value gt http localhost SpiraTeam lt value gt lt setting gt lt setting name Login serializeAs String gt lt value gt Yre dbl6ggs lt value gt lt setting gt lt setting name Password serializeAs String gt lt value gt Yre
175. is used for documentation purposes and is not actually used by the system Connection Info this should the full URL to the Bugzilla installation s web service API This is typically http lt Bugzilla server name gt xmlrpc cgi Login this should be set to a valid login to the Bugzilla installation typically an email address The login needs to have permissions to create and view bugs within Bugzilla Password this should be set to the password of the login specified above Time Offset normally this should be set to zero but if you find that issues being changed in Bugzilla are not being updated in SpiraTeam try increasing the value as this will tell the data synchronization plug in to add on the time offset in hours when comparing date time stamps Also if your Bugzilla installation is running on a server set to a different time zone then you should add in the number of hours difference between the servers time zones here Auto Map Users this is not currently used by the Bugzilla data sync plug in and can be ignored Custom 01 When connecting to Bugzilla sometimes the connection gets dropped by the server without notifying the plug in This happens when using HTTP 1 1 Keep Alive connections If you set this property to False it will tell the plug in to not use HTTP keep alives when connecting to Bugzilla otherwise set it to True Custom 02 When connecting to a Bugzilla instance that is running
176. is folder should already contain the DataSyncService exe and DataSyncService exe config files that are the primary files used for managing the data synchronization between Spiraleam and other systems If you do not have an on premise installation of SpiraTeam but instead are using a hosted subscription provided by Inflectra or a third party company you will not have access to the DataSyncService background service In such situations you should use the Desktop DataSync application instead This application is described in Appendix 1 and can be used instead of the server based DataSyncService 6 1 2 Configuring the Service To configure the integration service please open up the DataSyncService exe config file located in C Program Files Spiraleam Bin with a text editor such as Notepad Once open it should look like lt xml version 1 0 encoding utf 8 gt lt CONLLOUraLLOn gt CONTIGSeCt10nSs gt lt sectionGroup name applicationSettings type System Configuration ApplicationSettingsGroup System Version 2 0 0 0 Culture neutral PublicKeyToken b77a5c561934e089 gt lt section name Inflectra SpiraTest DataSyncService Properties Settings type System Configuration ClientSettingsSection System Version 2 0 0 0 Culture neutral PublickeyToken b77a5c561934e089 requirePermission false gt lt sectionGroup gt lt configSections gt lt applicationSettings gt lt Inflectra SpiraTest DataSyncService Properties Settings
177. is will bring up the Windows Service control panel SS Services Fle Acton View Help w Foe AM gt 2 On ee a Se a S SpiraTeam Data Sync Service Name Description Status Startup Type Log On As 4 Sy Secunty Accounts Manager Stores security information for local user acc Started Autornatic Local System Start the service Sy Security Center Monitors system security settings and config Automatic Local Syster Server Supports File print and named pipe sharing Started Automatic Local System Description By Shel Hardware Detection Provides notfications For AutoPlay hardware Started Artomatic Local System sanne e rath vin hen dR Sia Simple Mail Transfer Protocol SMTP Transports electronic mail across the network Manual Local System systems By Smart Card Manages access to smart cards read by this Marual Local Service ty SpiraTeam Dats Syne Service Manages the date synchronizetion between Local System SOLAgent SPIRA Local System Sy SQLSERVERAGENT Local Systern amp 550P Discovery Service Enables cescovery of UPnP devices on your h Local Service SG System Event Notification Tracks system events such as Windows lag Local Systern Sy System Restore Service Performs system restore Functions To stop Local System Sy Task Scheduler Enables a user to configure and schedule au j Local Systerh Sy TCP IP NetBIOS Helper Enables support For NetBIOS over TOPIP N Local Service Sia Telephony Provides Telephony API TAPT support For
178. iu Services Fle Action View Help Beoe AM gt Gy Services Local i Services Local SpiraTeam Data Sync Service Start the service Description Manages the data synchronization between SpiraTeam and other external systems Name Sy Secunty Accounts Manager By Security Center egy Server Sa Shell Hardware Detection Sia Simple Mail Transfer Protocol SMTP By Smart Card th SpiraTeam Data Syne Service By SQLAgentsSPIRA Hy SOLSERVERAGENT By SSOP Discovery Service Siy System Event Notification By System Restore Service Sf Task Scheduler Description Stores security information For local user acc Monitors system security settings and config Supports File print and named pipe sharing Provides notifications For AutoPlay hardware Transports etachronic mail across the network Manages access to smart cards read by this Enables cescovery of UPnP devices on your h Tracks system events such as Windows laga Performs system restore functions To stop Enables a user to configure and schedule au Status Started Started Started Startup Type Aornatic Automatic Automatic Akomatic Manual Maral Lag On As Local System Local Systern Local System Local System Local System Local Service Baya Local System Local Systern Local Service Local Systern Local System Local Systerh Local Service Local Systert lasal C bam Siy TCP IP NetBIOS Helper Siy Telephony a Talaa
179. l be synchronized with OnTime and needs to have at least Incident create modify view permissions and Release create modify view permissions in these projects Once you have made these changes save the file and proceed to the next stage 12 1 4 Configuring the Plug In The next step is to configure the plug in within SpiraTeam so that the system knows how to access the OnTime server To start the configuration please open up SpiralTeam in a web browser log in using a valid account that has System Administration level privileges and click on the System gt Data Synchronization administration option from the left hand navigation Data Synchronization Refresh SpiraTeam is able to communicate with a variety of external systems and applications using its background data synchronization service and library of available plug ins This page allows you to view add and modify the list of plug ins make changes to their configuration and verify the status of the most recent synchronization In addition you can force a particular plug in to perform a complete data synchronization by resetting its date of last sync OnTimeDataSync gt View Project Mappings 3 22 2010 11 20 02 PM Success gt Force Re Sync Edit Delete This screen lists all the plug ins already configured in the system Depending on whether you chose the option to include sample data in your installation or not you will see either an empty screen or a list of sample data sync
180. lease Notes Operating System Task Priority Status From this screen you need to click on Priority Severity and Status in turn to configure their values a Incident Status Click on the Status hyperlink under Incident Standard Fields to bring up the Incident status mapping configuration screen Edit Standard Field Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the BugzillaDataSync plug in next to each Spiraleam value Assigned T in ih a ASSIGNED Closed 5 CLOSED Duplicate 5 UNCONFIRMED if a New D Not Reproducible Open Reopen s REOPENED Resolved s RESOLVED The table lists each of the incident statuses available in SpiraTeam and provides you with the ability to enter the matching Bugzilla bug status for each one You can map multiple SpiraTeam fields to the same Bugzilla fields e g New and Open in SpiraTeam are both equivalent to NEW in Bugzilla in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from Bugzilla gt SpiraTeam We recommend that you always point the New and Open statuses inside SpiraTeam to point to the NEW status inside Bugzilla and make Open in SpiraTeam the Primary status of the two This is recommended so that as new incidents in SpiraTeam get synch
181. lect List Field Global all issues User Custom User Picker Issue type s Default Screen Global all issues b List Custom Properties This refers to custom properties that are either of type List or Multi List Click on the hyperlink of the list custom property under Incident Requirement Custom Properties to bring up the custom property mapping configuration screen For list custom properties there will be a textbox for both the custom field itself and a mapping table for each of the custom property values that need to be mapped Edit Custom Property Data Mapping JIRA DEMO Project Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Multi Select Field External Key 79004 l Custom Value Mapping Value 1 Value 2 Value 3 Value 4 First you need to lookup the ID of the custom field in JIRA that matches this custom property in Spiraleam This should be entered in the External Key field below the name of the custom property The ID can be found by looking at the URL inside JIRA when choosing to View Edit the Custom Field The URL will include the section id X where X is the numeric ID of the Custom Field inside JIRA Fields Custom Fields Custom Fiel
182. lues used in the two applications to be related to each other This is important as without a correct mapping there is no way for the integration service to know that an Enhancement in SpiraTeam is the same as a New Feature in JIRA for example The following mapping information needs to be setup in SpiraTeam The mapping of the project identifiers for the projects that need to be synchronized gt The mapping of users in the system The mapping of releases equivalent to JIRA versions in the system gt The mapping of the various standard fields in the system gt The mapping of the various custom properties in the system Each of these is explained in turn below 2 2 1 Configuring the Project Mapping From the data synchronization administration page you need to click on the View Project Mappings hyperlink next to the JIRA plug in name This will take you to the data mapping home page for the currently selected project JiraDataSync Project Data Mapping JIRA DEMO Project Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the JiraDataSync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name JIRA DEMO Project External Key DEMO Active Yes y Artifact Field Mapping
183. map multiple SpiraTeam fields to the same JIRA fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from JIRA gt SpiraTeam The JIRA ID can be found by looking at the URL inside JIRA when choosing to View Edit the Priority The URL will include the section id X where X is the numeric ID of the Priority inside JIRA View Priorities The table below shows the priorities used in this version of JIRA in order from highest to lowest Translate priorities Name Description con Order Operations Blocker Blocks development and or testing work production could not run Edit Delete Default Critical Crashes loss of data severe memory leak Edit Delete Default Major Major loss of function Edit Delete Default Minor Minor loss of function or other problem where easy workaround is present Edit Delete Default Trivial Cosmetic problem like misspelt words or misaligned text Edit Delete Default d Incident Severity Optional Click on the Severity hyperlink under Incident Standard Fields to bring up the Incident severity mapping configuration screen Edit Standard Field Data Mapping JIRA DEMO Project Change Project lt lt Back to Project May To configure the data mappings for this field please fill in the external key values for the JiraDataSync plug in next to each Spiraleam value Field Value 1 Critical 2
184. me Edit Configuration Issue type s Global all issues Default Value Edit Default Value Options Edit Options Value 1 Value 2 Value 3 Value 4 c JIRA s Component Field If your instance of JIRA requires that all new issues are submitted with a Component then you will need to fill out this section You first need to create an incident custom property in SpiraTeam of type Multi List that contains the various component names that exist inside JIRA Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping JIRA DEMO Project ch lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below lf this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Components aa ey Custom Value Mapping Component 1 Component 1 Component 2 First you need to enter the word Component as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to built in Component field in JIRA Next for each of the Property Values in the table in the lower half of the page you need to enter the JIRA Name not ID of the various Components
185. mend the following general processes be followed gt When running tests in SpiraTest or SpiraTeam defects found should be logged through the Test Execution Wizard as normal Developers using JIRA 4 x can log new defects into either SpiraTeam or JIRA In either case they will get loaded into the other system Once created in one of the systems and successfully replicated to the other system the incident should not be modified again inside SpiraTeam At this point the incident should not be acted upon inside SpiraTeam and all data changes to the issue should be made inside JIRA To enforce this you should modify the workflows set up in SpiraTeam so that the various fields are marked as inactive for all the incident statuses other than the New status This will allow someone to submit an incident in SpiraTeam but will prevent them making changes in conflict with JIRA after that point As the issue progresses through the customized JIRA workflow changes to the type of issue changes to its status priority description and resolution will be updated automatically in Spiraleam In essence Spiraleam acts as a read only viewer of these incidents You are now able to perform test coverage and incident reporting inside SpiraTest Spiraleam using the test cases managed by SpiraTest Spiraleam and the incidents managed on behalf of Spiral est Spiraleam inside JIRA 4 Using SpiraTest with Bugzilla This section outlines how to use Spi
186. n No Y Plan Effort 32 00 Available Effort 32 00 JiraDataSync ID 10000 In addition to the standard fields and custom properties you will see an additional text property called JiraDataSync ID that is used to store the mapped external identifier for the equivalent Version in JIRA You need to locate the ID of the equivalent version in JIRA enter it into this text box and click Save You should now repeat for all the other pre existing releases The JIRA ID can be found by looking at the URL inside JIRA when choosing to Edit the version s Build and Release The URL will include the numeric ID of the version inside JIRA in the URL in the example below the ID would be 10001 Workflows Screens Fields Version 1 1 09 Apr 13 Release Versions i Version 1 0 Build and Release Components Archive Delete Roles Permissions Issue Security Notifications ixforversion 10001 selectedTab com atlassian jira plugin ext ba 2 2 4 Configuring the Standard Field Mapping Now that the projects user and releases have been mapped correctly we need to configure the standard incident and requirement fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the JiraDataSync plug in entry JiraDataSync Project Data Mapping JIRA DEMO Project Change Project lt lt Back to Data Synchronization Home To configure this project for
187. n service to know that a New item in SpiraTeam is equivalent to a New item in RTC for example The following mapping information needs to be setup in Spiraleam gt The mapping of the project identifiers for the projects that need to be synchronized gt The mapping of the various standard fields in the system gt The mapping of the various custom properties in the system Each of these is explained in turn below 9 2 1 Configuring the Project Mapping From the data synchronization administration page you need to click on the View Project Mappings hyperlink next to the RTC plug in name This will take you to the data mapping home page for the currently selected project RtcDataSyne Project Data Mapping Sample Application Two Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the RtcDataSync plug in you need to specify the keyid of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Sample Application Two External Key Test Project Change Management Please click on each of the links below to configure the fleld level data mapping for each of the types of artifact that you will be synchronizing in this project Artifact Standard Fields Custom Properties Incident Priority Severity otatus Release Task Priority
188. n you need to enter the numeric ID for this user in Redmine This will allow the data synchronization plug in to know which user in Redmine matches this SpiraTeam user Click Update once you ve entered the appropriate ID value You should now repeat for the other users who will be active in both systems Project Membership Passwords amp Security Data Mapping RedmineData Sync ID 11 2 3 Configuring the Release Mapping Now that the projects and users have been mapped correctly we need to configure the mapping between Releases Iterations in SpiraTeam and Versions in Redmine To do this please navigate to Planning gt Releases and click on the Release Iteration in question Make sure you have the Overview tab visible and expand the Details section of the release iteration Release 1 0 0 0 Release 1 0 RL 000051 Release 1 0 Incidents Name Regs amp Tasks Test Cases Test Runs Attachments History Overview gt Details Version Creator 1 0 0 0 s2r2013 FE 9272013 A Go iO person days 192 00 1918 System Administrator T Start End Date Creation Date 6 27 2013 12 06 34 PM Resources Active 7 No 7 Available Effort 162 00 Yes Non Working Iteration Plan Effort RedmineDataSynce ID In addition to the standard fields and custom properties configured for Releases you will see an additional text property called RedmineDataSync ID
189. ncService background service In such situations you should use the Desktop DataSync application instead This application is described in Appendix 1 and can be used instead of the server based DataSyncService 10 1 3 Configuring the Service To configure the integration service please open up the DataSyncService exe config file located in C Program Files SpiralTeam Bin with a text editor such as Notepad Once open it should look like lt xml version 1 0 encoding utf 8 gt SCONLIGUraLion lt cConrigsections gt lt sectionGroup name applicationSettings type System Configuration ApplicationSettingsGroup System Version 2 0 0 0 Culture neutral PublicKeyToken b77a5c561934e089 gt lt section name Inflectra SpiraTest DataSyncService Properties Settings type System Configuration ClientSettingsSection System Version 2 0 0 0 Culture neutral PublickeyToken b77a5c561934e089 requirePermission false gt lt sectionGroup gt conftigsections gt lt applicationSettings gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt setting name PollingInterval serializeAs String gt lt value gt 600000 lt value gt lt setting gt lt setting name WebServiceUrl serializeAs String gt lt value gt http localhost SpiraTeam lt value gt lt setting gt lt setting name Login serializeAs String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name Password serialize
190. nce you have made these changes save the file and proceed to the next stage 10 1 4 Configuring the Plug In The next step is to configure the plug in within SpiraTeam so that the system knows how to access the OnTime server To start the configuration please open up SpiraTeam in a web browser log in using a valid account that has System Administration level privileges and click on the System gt Data Synchronization administration option from the left hand navigation Data Synchronization Refresh SpiraTeam is able to communicate with a variety of external systems and applications using its background data synchronization service and library of available plug ins This page allows you to view add and modify the list of plug ins make changes to their configuration and verify the status of the most recent synchronization In addition you can force a particular plug in to perform a complete data synchronization by resetting its date of last sync OnTimeDataSync gt View Project Mappings 12 2 2014 2 08 17 PM Success gt Force Re Sync Edit Delete View Errors This screen lists all the plug ins already configured in the system Depending on whether you chose the option to include sample data in your installation or not you will see either an empty screen or a list of sample data synchronization plug ins If you already see an entry for OnTimeDataSync you should click on its Edit link If you don t see such an entry in
191. nctions as Designed First you need to lookup the name of the field in ClearQuest that matches this custom property in Spiraleam This should be entered in the External Key field below the name of the custom property The easiest way to determine this is to use the ClearQuest Designer which lets you see all the fields associated with a ClearQuest defect E 7 0 0 admin connected 89 aim B Blank customer_severity BE Common Be DefectTracking amp Details General Field Information Version 1 loaded Help Text Record Types 5 A Defect Field Type Ed Fields Database Name 9 Attachments B Q customer Z dbid Artifact Ownership Q Description E Properties 53 Gj ClearQuest Database Admin Name Next for each of the Property Values in the table in the lower half of the page you need to enter the full name of the possible field values as displayed in the ClearQuest client application Once you have updated the various mapping sections you are now ready to start the service 8 3 Enabling the Data Synchronization 8 3 1 Starting the Service When SpiraTeam is installed a Windows Service SpiraTeam Data Sync Service is installed along with the web application However to avoid wasting system resources this service is initially set to run manually To ensure continued synchronization of SpiraTeam with ClearQuest we recommend starting the service and setting its startup
192. nfiguration and verify the status of the most recent synchronization In addition you can force a particular plug in to perform a complete data synchronization by resetting its date of last sync MsTfsDataSync gt View Project Mappings 8 17 2013 6 42 18 PM Success gt Force Re Sync Edit Delete View Errors This screen lists all the plug ins already configured in the system Depending on whether you chose the option to include sample data in your installation or not you will see either an empty screen or a list of sample data synchronization plug ins If you already see an entry for MsTfsDataSync you should click on its Edit link If you don t see such an entry in the list please click on the Add button instead In either case you will be taken to the following screen where you can enter or modify the TFS Data Synchronization plug in Edit Plug In MsTfsDataSync lt lt Back to Data Synchronization Home Please enter edit the following information for the plug in The exact information that needs to be entered is specific to each plug in and you should refer to the documentation for the plug in when entering changing it Name M sTfsDataSync Description This plug in allows incidents and tasks in the system to be synchronized with Microsoft Team Foundation Server TFS rah http vm tfs 3050 tfs DefaultCollection nro Login spira datasync Password ErAtEEEE Time Offset W Auto Map Users Custom 01
193. ng name Login serializeAs String gt lt value gt readbl6ggs lt value gt lt setting gt lt setting name Password serializeAs String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name EventLogSource serializeAs String gt lt value gt SpiraTeam Data Sync Service lt value gt lt setting gt lt setting name TraceLogging serializeAs String gt lt value gt False lt value gt lt setting gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt applicationSettings gt lt configuration gt The sections that need to be verified and possibly changed are marked in yellow above You need to check the following information gt The polling interval allows you to specify how frequently the data synchronization service will ask Spiraleam and the external system for new data updates The value is specified in milliseconds and we recommend a value no smaller than 5 minutes i e 300 000ms The larger the number the longer it will take for data to be synchronized but the lower the network and server overhead gt The base URL to your instance SpiraTeam It is typically of the form http lt server name gt SpiraTeam Make sure that when you enter this URL on a browser on the server itself the application login page appears gt Avvalid login name and password to your instance of SpiraTeam This user needs to be a member of the project s that will be synchronized with Clea
194. ngs gt At this point the incident can be worked on in either system with changes being synchronized to the other system However in general we recommend that the QA Testing team use SpiraTeam and the development team use TFS E g the developers will mark the bugs as resolved in MSTS once they have completed fixing them and the QA team will either reopen or close then in SpiraTeam once they have had a change to verify the resolution gt You are now able to perform test coverage and incident reporting inside SpiraTest Spiraleam using the test cases managed by SpiraTest SpiraTeam and the incidents managed collaboratively between SpiraTest SpiraTeam and TFS gt You can create project requirements and associated tasks in either SpiraTeam or TFS however the synchronization service is only unidirectional for requirements and tasks so when you create or update a requirement or task in TFS the change will be reflected in SpiraTeam but not the other way around 5 4 Troubleshooting In most cases once you have started the service once it s up and running you will not see any error or warning messages from the Data Sync service However if you have new users created in Spiraleam that have not been mapped to users in TFS when you assign incidents requirements or tasks to those items you may see warning messages in the Event Viewer letting you Know which users needs to be mapped 5 5 TFS Field Reference The following fields are a
195. nistration gt Users gt View Edit Users which will bring up the list of users in the system Then click on the Edit button for a particular user that will be editing cases in FogBugz Add Edit User Fred Bloggs Please review the information listed below and make any changes if necessary Once you have finished click Update Insert to confirm them First Name Middle Initial Last Name User Name Email Address fredblogqgs mycompany com System Administrator Active User FogBugzData Sync ID L JLDAP Managed User LDAP DN L_ Change Password You will notice that below the Active flag for the user is a list of all the configured data synchronization plug ins In the text box next to the FogBugz Data Sync plug in you need to enter the ID of this user in FogBugz This will allow the data synchronization plug in to know which user in SpiraTeam match which equivalent user in FogBugz The ID can be found in FogBugz by going to Settings gt Users Name Email Status Description E Fred Bloggs fredbloggs inflectra com Active No email E joesmith joesmith inflectra com DA Active E System Administrator webmaster inflectra com Active Site Admin Add New Person Then hover the mouse over the user s name The user ID will be displayed in the URL line as ixPerson X where X is the numeric ID of the user Back in SpiraTeam click Update once you ve entered the appropriate user ID in the mapping box Y
196. not being updated in SpiraTeam try increasing the value as this will tell the data synchronization plug in to add on the time offset in hours when comparing date time stamps Also if your JIRA installation is running on a server set to a different time zone then you should add in the number of hours difference between the servers time zones here Auto Map Users This changes the way that the plugin maps users in SpiraTeam to those in JIRA gt Auto Map True With this setting all users in SpiraTeam need to have the same username as those in JIRA If this is the case then you do not need to perform the user mapping task outlined in section 2 2 2 This is a big time saver if you can guarantee that all usernames are the same in both systems gt Auto Map False With this setting users in SpiraTeam and JIRA are free to have different usernames because you specify the corresponding JIRA name for each user as outlined in section 2 2 2 Custom 01 This is used to specify a JIRA custom property that should be mapped to the built in SpiraTeam Incident Severity field which does not exist in JIRA This can be left empty for now and will be discussed below in section 2 2 Custom 02 This should be set to the word True if you want to have the new issues submitted to JIRA be submitted using a specified SecurityLevel If you re not using the security level feature of JIRA leave the field blank Custom 03 This should be se
197. not seen before it will create a corresponding Release in OnTime Similarly if it comes across a new Release in OnTime that it has not seen before it will create a new Release in SpiraTeam Therefore when using both systems together it is recommended that you only enter new Releases in one system and let the data synchronization service add them to the other system To see this mapping inside SpiraTeam navigate to Planning gt Releases and click on the Release Iteration in question Make sure you have the Overview tab visible and expand the Details section of the release iteration Release 3 0 0 1 New Release RL 000024 Name Overview Incidents Regs amp Tasks Test Cases Test Runs Attachments History v Details Start End Date Creation Date 6 5 2013 6 07 56 PM Resources Active Ys v Non Working person days Iteration No v oH Plan Effort i Available Effort 176 00 In addition to the standard fields and custom properties configured for Releases you will see an additional text property called OnTimeDataSync ID that is used to store the mapped external identifier for the equivalent Version in OnTime 10 2 4 Configuring the Standard Field Mapping Now that the projects user and releases have been mapped correctly we need to configure the standard incident fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mapping
198. o configure the fleld level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority Operating System Severity Status HOM rropenlles K Release Task Priority Status From this screen you need to set up the Priority Severity Status and Type fields a Incident Type The Incident Type field is optional and can be linked to the Mantis Category selection If you do not link values then all issues being imported into SpiraTeam from Mantis will be set to the Default Type as specified in the View Edit Types screen and issues going from SpiraTeam into Mantis will be assigned to the first Category in the list Usually Mantis orders them alphabetically but this may change depending on your installation If you do not have any Categories set up then issues will not transfer over and error messages will be logged For existing issues updates to this field will not be transferred i gi Enhancement Yes Po Incident Yes Limitation Yes ee New Value Yes fe Training Yes Yes a Let a i Let LP m i sll sll ells Ke lt 4 lt 4 dl lt 4 The table lists each of the incident types available in SpiraTeam and provides you with the ability to enter the matching Mantis Category for each one The value to put in External ID is the Category text Edit Project Category aaa Assigned To z Update Category The Mantis
199. o zero but if you find that work items being changed in TFS are not being updated in SpiraTeam try increasing the value as this will tell the data synchronization plug in to add on the time offset in hours when comparing date time stamps Also if your TFS installation is running on a server set to a different time zone then you should add in the number of hours difference between the servers time zones here The remaining fields work differently depending on which version of the TFS plugin you are using 2012 2010 or 2005 2008 a TFS 2012 Plugin Please fill out the fields as follows gt Auto Map Users This changes the way the plugin maps users in SpiraTeam to those in TFS gt Auto Map True With this setting all users in SpiraTeam need to have the same username as those in TFS If this is the case then you do not need to perform the user mapping task outlined in section 5 2 2 This is a big time saver if you can guarantee that all usernames are the same in both systems gt Auto Map False With this setting users in SpiraTeam and TFS are free to have different usernames because you specify the corresponding TFS name for each user as outlined in 5 2 2 gt Custom 01 This is used to specify the Windows Active Directory Domain that the Windows user specified above is a member of If you are running TFS on a Windows workgroup just use the server name and make sure that the Windows user above is a user on that server itsel
200. ocesses be followed gt When running tests in SpiraTeam defects found should be logged through the Add Incident option as normal gt Once an incident has been created during the running of the test it will now be populated across into OnTime as a defect It will be populated with the information captured in SpiraTeam gt At this point the incident should not be acted upon inside SpiraTeam and all data changes to the defect should be made inside OnTime To enforce this you can modify the workflows set up in Spiraleam so that the various fields are marked as inactive for all the incident statuses other than the New status This will allow someone to submit an incident in SpiraTeam but will prevent them making changes in conflict with OnTime after that point gt As the defect progresses through the OnTime workflow changes to the status priority severity and resolution will be updated automatically in SpiraTeam In essence SpiraTeam acts as a read only viewer of these incidents gt You are now able to perform test coverage and incident reporting inside SpiraTeam using the test cases managed by SpiraTeam and the incidents managed on behalf of SpiraTeam inside OnTime Appendix 1 Desktop Data Sync Overview The Desktop Data Synchronization utility hereafter referred to as the Desktop DataSync is a standalone utility than can be used to run the various Data Synchronization Pluglns without a serve
201. oking at the URL inside JIRA when choosing to View Edit the Custom Field The URL will include the section id X where X is the numeric ID of the Custom Field inside JIRA e Requirement Status Optional Click on the Status hyperlink under Requirement Standard Fields to bring up the Requirement status Mapping configuration screen Edit Standard Field Data Mapping JIRA DEMO Project Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the JiraDataSync plug in next to each SpiraTeam value Accepted Yes 4 Completed Yes Evaluated Yes 4 In Progress Yes a Obsolete Yes a Planned b lt lt a lt Rejected a Requested lt The table lists each of the requirement statuses available in SpiraTeam and provides you with the ability to enter the matching JIRA issue status ID for each one You can map multiple SpiraTeam fields to the same JIRA fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from JIRA gt SpiraTeam The JIRA ID can be found by looking at the URL inside JIRA when choosing to View Edit the Issue Status The URL will include the section id X where X is the numeric ID of the Issue Status inside JIRA Status Details Mode Workflows Operations 4 Open Active jira Edit The issue
202. om property values used in the two applications to be related to each other This is important as without a correct mapping there is no way for the integration service to know that an Enhancement in SpiraTeam is the same as a New Feature in JIRA for example The following mapping information needs to be setup in SpiraTeam gt The mapping of the project identifiers for the projects that need to be synchronized gt The mapping of users in the system gt The mapping of releases equivalent to JIRA versions in the system The mapping of the various standard fields in the system gt The mapping of the various custom properties in the system Each of these is explained in turn below 3 2 1 Configuring the Project Mapping From the data synchronization administration page you need to click on the View Project Mappings hyperlink next to the JIRA plug in name This will take you to the data mapping home page for the currently selected project View Edit Project Data Mapping Library Information System Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the JiraData Sync plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different fields that need to be mapped for the synchronization to operate Project Name Library Information System Artifact Field Mapping Please click
203. ommend immediately stopping the SpiraTeam service and checking the various mapping entries If you cannot see any issues with the mapping information we recommend sending a copy of the event log message s to Inflectra customer services http www inflectra com Support who will help you troubleshoot the problem To use SpiraTeam with RTC on an ongoing basis we recommend the following general processes be followed gt When running tests in SpiraTest or SpiraTeam defects found should be logged through the Test Execution Wizard as normal gt Developers using RTC can log new work items into either SpiraTeam or RTC In either case they will get loaded into the other system gt Once created in one of the systems and successfully replicated to the other system the incident should not be modified again inside SpiraTeam gt At this point the incident should not be acted upon inside SpiraTeam and all data changes to the issue should be made inside RTC To enforce this you should modify the workflows set up in SpiraTeam so that the various fields are marked as inactive for all the incident statuses other than the New status This will allow someone to submit an incident in SpiraTeam but will prevent them making changes in conflict with RTC after that point gt As the issue progresses through the customized RTC workflow changes to the type of work item changes to its status description and custom fields will be updated autom
204. on from JIRA gt SpiraTeam The JIRA ID can be found by looking at the URL inside JIRA when choosing to View Edit the Priority The URL will include the section id X where X is the numeric ID of the Priority inside JIRA View Priorities The table below shows the priorities used in this version of JIRA in order from highest to lowest Translate priorities Name Description Order Operations Blocker Blocks development and or testing work production could not run Edit Delete Default Critical Crashes loss of data severe memory leak Edit Delete Default Major Major loss of function Edit Delete Default Minor Minor loss of function or other problem where easy workaround is present Edit Delete Default Trivial Cosmetic problem like misspelt words or misaligned text Edit Delete Default 2 2 5 Configuring the Custom Property Mapping Now that the various SpiraTeam standard fields have been mapped correctly we need to configure the custom property mappings This is used for both custom properties in SpiraTeam that map to custom fields in JIRA and also for custom properties in SpiraTeam that are used to map to standard fields in JIRA Component Environment Resolution and SecurityLevel that don t exist in SpiraTeam From the View Edit Project Data Mapping screen you need to click on the name of the Incident or Requirement Custom Property that you want to add data mapping information for We will consider the
205. on from JIRA gt SpiraTeam Note The JIRA ID can be found by looking at the URL inside JIRA when choosing to View Edit the Priority The URL will include the section id X where X is the numeric ID of the Priority inside JIRA d Incident Severity Optional Click on the Severity hyperlink under Incident Standard Fields to bring up the Incident severity mapping configuration screen 1 Critical 2 High 3 Medium 4 Low Unlike the other incident standard fields JIRA doesn t actually have a built in field for storing the severity of an issue so if you want to be able to see the SpiralTeam incident severity in JIRA you ll need to create a JIRA custom list field to store the different severity values If you don t want to synchronize severity values with JIRA you can skip the rest of this section Once you have created a custom field in JIRA to contain the list of severity values you need to now populate the above table with the name Not the ID of the severity custom property values inside JIRA and click Update Secondly you need to go to the Plug in configuration screen Edit Plug In JiraDataSync lt lt Back to Data Synchronization Home Please enter edit the following information for the plug in The exact information that needs to be entered is specific to each plug in and you should refer to the documentation for the plug in when entering changing it Name iraDataSync Description This plug in allo
206. on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Priority Notes Severity Operating System Status Type Release Notes Operating System Task Priority Status If the project name does not match the name of the project you want to configure the data mapping for click on the Change Project hyperlink to change the current project To enable this project for data synchronization with JIRA you need to enter gt External Key This should be set to the name of the project token in JIRA Typically this is a three letter acronym for the project gt Active Flag Set this to Yes so that SpiraTeam knows that you want to synchronize data for this project Once the project has been completed setting the value to No will stop data synchronization reducing network utilization Click Update to confirm these settings Once you have enabled the project for data synchronization you can now enter the other data mapping values outlined below Note Once you have successfully configured the project when creating a new project you should choose the option to Create Project from Existing Project rather than Use Default Template so that all the project mappings get copied across to the new project 3 2 2 Configuring the User Mapping To configure the mapping of users in the two systems you need to
207. on of the plug in This is an optional field that is used for documentation purposes and is not actually used by the system gt Connection Info this should be the base URL of the Redmine installation As an example for the public demo installation of Redmine it would be http demo redmine org Login this should be set to a valid login to the Redmine installation the login needs to have permissions to create and view bugs and versions within Redmine gt Password this should be set to the password of the login specified above gt Time Offset normally this should be set to zero but if you find that issues being changed in Redmine are not being updated in SpiraTeam try increasing the value as this will tell the data synchronization plug in to add on the time offset in hours when comparing date time stamps Also if your Redmine installation is running on a server set to a different time zone then you should add in the number of hours difference between the servers time zones here gt Auto Map Users This changes the way that the plugin maps users in Spiraleam to those in Redmine gt Auto Map True With this setting all users in SpiraTeam need to have the same username as those in Redmine If this is the case then you do not need to perform the user mapping task outlined in section 11 2 2 This is a big time saver if you can guarantee that all usernames are the same in both systems gt Auto Map False With
208. on the Type hyperlink under Incident Standard Fields to bring up the Incident type mapping configuration screen Bug E Change Request ah lt lt aag A A 4 Enhancement Incident Issue Limitation Risk Training External Key O The table lists each of the incident types available in SpiraTeam and provides you with the ability to enter the matching JIRA issue type ID for each one You can map multiple SpiraTeam fields to the same JIRA fields e g Bug and Incident in SpiraTeam are both equivalent to Bug in JIRA in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from JIRA gt SpiraTeam Note The JIRA ID can be found by looking at the URL inside JIRA when choosing to View Edit the Issue Type The URL will include the section id X where X is the numeric ID of the Issue Type inside JIRA b Incident Status Click on the Status hyperlink under Incident Standard Fields to bring up the Incident status mapping configuration screen Assigned z a Closed Duplicate New Not Reproducible Alla e E lt A Open Reopen a Resolved al The table lists each of the incident statuses available in SpiraTeam and provides you with the ability to enter the matching JIRA issue status ID for each one You can map multiple SpiraTeam fields to the same JIRA fields e g New and Open in S
209. onnecting to FogBugz otherwise set it to True gt Custom 02 When connecting to a FogBugz instance that is running under HTTPS SSL this custom property can be set to determine if the plug in should verify that the SSL certificate is a trusted root certificate Set to True if you are using an SSL certificate that was issued by a trusted Certification Authority and set to False if you are using a self signed certificate gt Custom 03 Normally all rich text HTML descriptions in SpiraTeam are converted into plain text when added to FogBugz However more recent version of FogBugz can now support rich text So if you have rich text enabled in your instance of FogBugz you should enter the world True in Custom 03 to enable rich text description transfer gt Custom 04 05 these are not currently used by the FogBugz data sync plug in and can be left blank 6 2 Configuring the Data Mapping Next you need to configure the data mapping between Spiraleam and FogBugz This allows the various projects users releases incident types statuses priorities and custom property values used in the two applications to be related to each other This is important as without a correct mapping there is no way for the integration service to know that an Enhancement in SpiraTeam is the same as a Feature in FogBugz for example The following mapping information needs to be setup in SpiraTeam gt The mapping
210. oth systems together it is recommended that you only enter new Releases Versions in one system and let the data synchronization service add them to the other system However you may start out with the situation where you already have pre existing Releases Version in both systems that you need to associate in the data mapping If you don t do this you may find that duplicates get created when you first enable the data synchronization service Therefore for any Releases Iterations that already exist in BOTH systems please navigate to Planning gt Releases and click on the Release Iteration in question Make sure you have the Overview tab visible and expand the Details section of the release iteration Release 61 0 1 0 RL 000071 Name Overview Incidents Regs amp Tasks Test Cases Test Runs Attachments Details Start End Date aro2013 A 452013 M Creation Date 4 11 2013 4 58 18 PM Resources A Active Yes Y Non Working oF person days Iteration No 7 Plan Effort 32 00 Available Effort 32 00 JiraDataSync ID 40000 In addition to the standard fields custom properties configured for Releases you will see an additional text property called JiraDataSync ID that is used to store the mapped external identifier for the equivalent Version in JIRA You need to locate the ID of the equivalent version in JIRA enter it into this text box and click Save You should now repeat for all the other pre
211. ou should now repeat for the other users who will be active in both systems 6 2 3 Configuring the Release Mapping When the data synchronization service runs when it comes across a release iteration in SpiraTeam that it has not seen before it will create a corresponding Release Fix For in FogBugz Similarly if it comes across a new Release Fix For in FogBugz that it has not seen before it will create a new Release in Spiraleam Therefore when using both systems together it is recommended that you only enter new Releases Versions in one system and let the data synchronization service add them to the other system However you may start out with the situation where you already have pre existing Releases Versions in both systems that you need to associate in the data mapping If you don t do this you may find that duplicates get created when you first enable the data synchronization service Therefore for any Releases Iterations that already exist in BOTH systems please navigate to Planning gt Releases and click on the Release Iteration in question Make sure you have the Overview tab visible and expand the Details section of the release iteration Release 2 0B Version 2 0B RL 000022 Name Version 2 0B Overview Incidents Regs amp Tasks Test Cases Test Runs Attachments History v Details id Version Creator Start End Date Creation Date 6 5 2013 6 00 56 PM Resources Active Non Wo
212. ou will notice that below the Active flag for the user is a list of all the configured data synchronization plug ins In the text box next to the TFS Data Sync plug in you need to enter the full name of this Windows User not the login This is the name of the user as they appear inside work items within TFS Assigned to Administrator pa This will allow the data synchronization plug in to know which user in SpiraTeam match which equivalent user in TFS Click Update once you ve entered the appropriate login name You should now repeat for the other users who will be active in both systems If you have set the Auto Map Users option in the TFS 2012 plugin you can skip this section completely 5 2 3 Configuring the Release Mapping When the data synchronization service runs when it comes across a release iteration in Spiraleam that it has not seen before it will create a corresponding Iteration in TFS Similarly if it comes across a new Iteration in TFS that it has not seen before it will create a new Release Iteration in SpiraTeam Therefore when using both systems together it is recommended that you only enter new Releases Iterations in one system and let the data synchronization service add them to the other system However you may start out with the situation where you already have pre existing Releases Iterations in both systems that you need to associate in the data mapping If you don t do this you may find that dupl
213. ource serializeAs String gt lt value gt SpiraTeam Data Sync Service lt value gt lt setting gt lt setting name TraceLogging serializeAs String gt lt value gt False lt value gt lt setting gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt applicationSettings gt lt configuration gt The sections that need to be verified and possibly changed are marked in yellow above You need to check the following information gt The polling interval allows you to specify how frequently the data synchronization service will ask Spiraleam and the external system for new data updates The value is specified in milliseconds and we recommend a value no smaller than 5 minutes i e 300 000ms The larger the number the longer it will take for data to be synchronized but the lower the network and server overhead gt The base URL to your instance SpiraTeam It is typically of the form http lt server name gt SpiraTeam Make sure that when you enter this URL on a browser on the server itself the application login page appears gt Avvalid login name and password to your instance of SpiraTeam This user needs to be a member of the project s that will be synchronized with Bugzilla and needs to have at least Incident create modify view permissions and Release create modify view permissions in these projects Once you have made these changes save the file and proceed to the next stage 4 1 3 Configuring the Pl
214. p Local Systeri a i Talaa Cashjas emenmbe se ba han be be lasal O ebam extended A Standard Click on the SpiraTeam Data Sync Service entry and click on the link to start the service Then right click the service entry and choose the option to set the startup type to Automatic This will ensure that synchronization continues between SpiralTeam and Bugzilla after a reboot of the server 4 3 2 Using SpiraTest with Bugzilla Now that the integration service has been configured and the service started initially any incidents created in SpiraTeam for the specified projects will be imported into Bugzilla At this point we recommend opening the Windows Event Viewer and choosing the Application Log In this log any error messages raised by the Data Synchronization service will be displayed If you see any error messages at this point we recommend immediately stopping the service and checking the various mapping entries If you cannot see any issues with the mapping information we recommend sending a copy of the event log message s to Inflectra customer services Support inflectra com who will help you troubleshoot the problem To use SpiraTeam with Bugzilla on an ongoing basis we recommend the following general processes be followed gt When running tests in SpiraTeam defects found should be logged through the Add Incident option as normal gt Once an incident has been created during the r
215. patible with SpiraTeam v3 0 and TFS 2010 e The MS TFS 2012 plugin is compatible with SpiraTeam v4 0 and TFS 2012 In general to get the most functionality we recommend using the latest version of the plugin that is compatible with your installed versions of SpiraTeam and TFS If you have a version of SpiralTeam that predates v2 2 you will need to upgrade to at least v2 2 before trying to integrate with TFS The steps that need to be performed to configure integration with TFS are as follows Download the latest TFS Data Sync plug in for SpiraTeam from our website Vv setup the plug in in SpiraTeam to point to the correct instance of TFS gt Configure the data field mappings between SpiraTeam and TFS gt Start the service and verify data transfer 5 1 1 Download the TFS Plug In Go to the Inflectra website and open up the page that lists the various downloads available for SpiraTeam http www inflectra com Spira leam Downloads aspx Listed on this page will be the TFS Plug Ins for Spiraleam Right click on the link for the appropriate version 2005 2008 2010 or 2012 and save the Zip compressed folder to the hard drive of the server where SpiralTeam is installed Open up the compressed folder and extract the MsTfsDataSync dll file and place in the C Program Files SpiraTeam Bin folder it may be SpiraTest or SpiraPlan depending on which product you re running This folder should already contain the DataSyncService exe and DataSyn
216. piraTeam are both equivalent to Open in JIRA in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from JIRA gt SpiraTeam We recommend that you always point the New and Open statuses inside SpiraTeam to point to the ID for Open inside JIRA and make Open in SpiraTeam the Primary status of the two This is recommended so that as new incidents in SpiraTeam get synched over to JIRA they will get switched to the Open status in JIRA which will then be synched back to Open in SpiraTeam That way you ll be able to see at a glance which incidents have been synched with JIRA and those that haven t Note The JIRA ID can be found by looking at the URL inside JIRA when choosing to View Edit the Issue Status The URL will include the section id X where X is the numeric ID of the Issue Status inside JIRA c Incident Priority Click on the Priority hyperlink under Incident Standard Fields to bring up the Incident Priority mapping configuration screen 1 Critical 2 High 3 Medium 4 Low The table lists each of the incident priorities available in SpiraTeam and provides you with the ability to enter the matching JIRA priority ID for each one You can map multiple SpiraTeam fields to the same JIRA fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronizati
217. r installation of SpiraTest SpiraPlan or SpiraTeam hereafter Spira This is useful where you have the Spira instance hosted externally and do not have access to the server Installation To obtain the Desktop DataSync go to the Inflectra website and under the Downloads and Add Ons section you will find a Windows Installation MSI package that will install the Desktop DataSync onto your computer Next you need to download the appropriate plug in s for the various bug trackers as described in the appropriate section of this document and place the assemblies DLL files into the same folder that contains the DesktopDataSync exe application Usage Once you have downloaded and installed the application and appropriate plug ins go to Start gt Programs gt Inflectra gt Desktop DataSync to launch the application This will bring up the main options window of the application S Spira DataSync Options EW Spira Desktop Data Sync S nmr Please enter or edit the data synchronization options below Spira URL http localhost SpiraT est User Name Administrator Passion ae Test Settings Folling Interval 2 minutes Enable Trace Logging M Start Cancel You should then enter the URL login and password to your Spira installation and click Test Assuming that this information is correct you will see a confirmation message Spira Desktop Data Sync Please enter or edit the data synchronization option
218. rQuest and needs to have at least Incident create modify view permissions and Release create modify view permissions in these projects Once you have made these changes save the file and proceed to the next stage 8 1 3 Configuring the Plug In The next step is to configure the plug in within SpiraTeam so that the system knows how to access the ClearQuest server To start the configuration please open up SpiraTeam in a web browser log in using a valid account that has System Administration level privileges and click on the System gt Data Synchronization administration option from the left hand navigation Data Synchronization Refresh Spiraleam is able to communicate with a variety of external systems and applications using its background data synchronization service and library of available plug ins This page allows you to view add and modify the list of plug ins make changes to their configuration and verify the status of the most recent synchronization In addition you can force a particular plug in to perform a complete data synchronization by resetting its date of last sync ClearQuestDataSync gt View Project Mappings 9 13 2011 4 02 19 PM Success gt Force Re Sync Edit Delete This screen lists all the plug ins already configured in the system Depending on whether you chose the option to include sample data in your installation or not you will see either an empty screen or a list of sample data synchronization plu
219. raTeam so that the system knows how to access the RTC server To start the configuration please open up SpiraTeam in a web browser log in using a valid account that has System Administration level privileges and click on the System gt Data Synchronization administration option from the left hand navigation Data Synchronization Refresh SpiraTeam is able to communicate with a variety of external systems and applications using its background data synchronization service and library of available plug ins This page allows you to view add and modify the list of plug ins make changes to their configuration and verify the status of the most recent synchronization In addition you can force a particular plug in to perform a complete data synchronization by resetting its date of last sync BugzillaDataSync gt View Project Mappings Failure gt Force Re Synec Edit Delete FogBugzDataSync gt View Project Mappings Failure gt Force Re Sync Edit Delete JiraDataS yne gt View Project Mappings Failure gt Force Re Sync Edit Delete MsTfsDataSync gt View Project Mappings Failure gt Force Re Sync Edit Delete RtcDataSync gt View Project Mappings 5 31 2012 1 35 37 PM Success gt Force Re Syne Edit Delete This screen lists all the plug ins already configured in the system Depending on whether you chose the option to include sample data in your installation or not you will see either an empty screen or a list of
220. raTeam using the test cases managed by SpiraTeam and the incidents managed on behalf of SpiraTeam inside OnTime 11 Using SpiraTeam with Redmine This section outlines how to use SpiraTeam in conjunction with the open source Redmine bug tracking and project management system The built in integration service allows the quality assurance team to manage their requirements and test cases in Spiraleam execute test runs in SpiraTeam and then have the new incidents generated during the run be automatically loaded into Redmine Once the incidents are loaded into Redmine as issues the development team can then manage the lifecycle of these issues in Redmine and have the status changes in Redmine be reflected back in SpiraTeam In addition any issues logged directly into Redmine will get imported into SpiraTeam so that they can be linked to test cases and requirements 11 1 Configuring the Integration Service This section outlines how to configure the integration service to export incidents into Redmine and pick up subsequent status changes made in Redmine and have them update SpiraTeam It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam hereafter referred to generically as Spiraleam v4 0 or later and a working installation of Redmine v2 0 or later If you have an earlier version of SpiraTeam you will need to upgrade to at least v4 0 before trying to integrate with Redmine The steps that need to be pe
221. raTest in conjunction with the open source Bugzilla bug tracking system The built in integration service allows the quality assurance team to manage their requirements and test cases in SpiraTest execute test runs in SpiraTest and then have the new incidents generated during the run be automatically loaded into Bugzilla Once the incidents are loaded into Bugzilla as bugs the development team can then manage the lifecycle of these bugs in Bugzilla and have the status changes in Bugzilla be reflected back in SpiraTest In addition if you are using Bugzilla 4 x or higher any issues logged directly into Bugzilla will get imported into SpiraTeam so that they can be linked to test cases and requirements 4 1 Configuring the Integration Service This section outlines how to configure the integration service to export incidents into Bugzilla and pick up subsequent status changes made in Bugzilla and have them update SpiraTeam It assumes that you already have a working installation of SpiraTest SpiraPlan or SpiraTeam v2 2 or later and a working installation of Bugzilla v3 0 or later If you have an earlier version of SpiraTeam you will need to upgrade to at least v2 2 before trying to integrate with Bugzilla The steps that need to be performed to configure integration with Bugzilla are as follows gt Download the latest Bugzilla Data Sync plug in for SpiraTeam from our website gt There are separate plug ins for Bugzilla 3 x and Bugzilla 4 x so
222. rate all their users over to Spiraleam Therefore SpiraPlan SpiraTest and Spiraleam are capable of integrating with a variety of commercial and open source bug tracking systems This guide outlines how to integrate and use SpiraTest SpiraPlan and SpiraTeam in conjunction with other external Bug Issue Tracking systems This guide assumes that the reader is familiar with both SpiraTeam and the appropriate tool being discussed For information regarding how to use SpiraTeam please refer to the Spiraleam User Manual Each of the sections covers a different tool so we recommend using the table of contents on the left to locate the tool you re looking to either integrate or migrate from then read the installation and usage instructions 2 Using SpiraTeam with JIRA 5 This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with the JIRA issue bug tracking system version 5 0 and later The built in integration service allows the quality assurance team to manage their requirements and test cases in SpiraTeam execute test runs in SpiraTest and then have the new incidents generated during the run be automatically loaded into JIRA Once the incidents are loaded into JIRA as issues the development team can then manage the lifecycle of these issues in JIRA and have the status changes in JIRA be reflected back in SpiraTeam In addition any issues logged directly into JIRA will
223. ration screen Edit Standard Field Data Mapping Redmine Demo Project Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the RedmineDataSync plug in next to each SpiraTeam value 3 Medium 4 Low 3 The table lists each of the incident priorities available in SpiraTeam and provides you with the ability to enter the matching Redmine priority ID for each one You can map multiple SpiraTeam fields to the same Redmine fields in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from Redmine gt SpiraTeam c Incident Type Incident types in SpiraTeam are equivalent to Trackers in Redmine Click on the Type hyperlink under Incident Standard Fields to bring up the Incident type mapping configuration screen Edit Standard Field Data Mapping Redmine Demo Project Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the RedmineDataSync plug in next to each Spiraleam value Bug j i Change Request a Enhancement j i Incident a Issue i Limitation a Risk a Training The table lists each of the incident types available in SpiraTeam and provides you with the ability to enter the matching Redmine Tra
224. renamed the JiraDataSync dll file for any reason then you need to change the name here to match gt Description this should be set to a description of the plug in This is an optional field that is used for documentation purposes and is not actually used by the system gt Connection Info this should the full URL to the JIRA installation s web service API This is typically http lt jira server name gt rpc soap jirasoapservice v2 Login this should be set to a valid login to the JIRA installation The login needs to have permissions to create and view issues and versions within JIRA gt Password this should be set to the password of the login specified above gt Time Offset normally this should be set to zero but if you find that issues being changed in JIRA are not being updated in SpiraTeam try increasing the value as this will tell the data synchronization plug in to add on the time offset in hours when comparing date time stamps Also if your JIRA installation is running on a server set to a different time zone then you should add in the number of hours difference between the servers time zones here The remaining fields work differently depending on which version of the plugin you are using JIRA 3 x or JIRA 4 x a JIRA 3 x Plugin Please fill out the fields as follows gt Auto Map Users this is not currently used and can be ignored gt Custom 01 This is used to specify a JIRA custom property
225. rformed to configure integration with Redmine are as follows Download the latest Redmine Data Sync plug in for Spiraleam from our website Vv Setup the plug in in SpiraTeam to point to the correct instance of Redmine gt Configure the data field mappings between SpiraTeam and Redmine gt Start the service and verify data transfer 11 1 1 Download the Redmine Plug In Go to the Inflectra website and open up the page that lists the various downloads available for SpiraTeam hittp www inflectra com Spiraleam Downloads aspx Listed on this page will be the Redmine Plug In for SpiraTeam Right click on this link and save the Zip compressed folder to the hard drive of the server where SpiraTeam is installed Open up the compressed folder and extract the RedmineDataSync dll file and place it in the C Program Files SpiraTeam Bin folder it may be SpiraTest or SpiraPlan depending on which product you re running This folder should already contain the DataSyncService exe and DataSyncService exe config files that are the primary files used for managing the data synchronization between SpiraTeam and other systems If you do not have an on premise installation of SpiraTeam but instead are using a hosted subscription provided by Inflectra or a third party company you will not have access to the DataSyncService background service In such situations you should use the Desktop DataSync application instead This application is described in Appendix
226. rking person days Iteration Plan Effort 176 00 Available Effort 176 00 In addition to the standard fields and custom properties configured for Releases you will see an additional text property called FogBugzDataSync ID that is used to store the mapped external identifier for the equivalent Release in FogBugz You need to locate the ID of the equivalent Release in FogBugz enter it into this text box and click Save You should now repeat for all the other pre existing releases The FogBugz Release ID can be found by going to Settings gt Projects and viewing the releases Releases e Version Date this project 1 0 0 0f1 fi 5 30 2009 v2 06 e 6 8 2009 v2 0C Fi 6 15 2009 EF Create New Release A list of past and upcoming releases or versions specific to this project for example Beta Version 2 0 etc Then hover the mouse over the release name The release ID will be displayed in the URL line as IxFixFor X where X is the numeric ID of the release 6 2 4 Configuring the Standard Field Mapping Now that the projects user and releases have been mapped correctly we need to configure the standard incident fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the FogBugzDataSync plug in entry Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact
227. rkltemTracking database in TFS 2010 it will named after your project collection instead and locating the IreeNodes table TypelD ParentID gt 41 1 42 Library Information System 2 43 Project Iteration 44 Iteration 1 44 Iteration 2 44 Iteration O 43 Project Structure 44 Iteration 3 45 Iteration 3 1 45 Iteration 3 2 Poo 4y o On eR MN e Jow mM oF mM M Ne Oo 2 Once you have found the matching Iteration by name the numeric value stored in the ID column the one on the left is the value that needs to get added as the MsTfsDataSync ID inside SpiraTeam 5 2 4 Configuring the Standard Incident Field Mapping Now that the projects user and releases have been mapped correctly we need to configure the standard incident fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the MsTfsDataSync plug in entry Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Requirement Importance Status Test Case Prionty Incident FPrionty I k Rank Release Task From this screen you need to click on Priority Severity Status and Type in turn to configure their values a Incident Type Click on the Type hyperlink under Incident Standard Fields to bring up the Incident type mapping configuration scr
228. rlink of this new text custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the BugzillaDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Resolution External Key Resolution Custom Value Mapping All you need to do on this screen is enter the word Resolution in the External Key textbox and the data sync plug in will know that this custom property is mapped to the built in Resolution field in Bugzilla Once you have updated the various mapping sections you are now ready to start the service 4 3 Enabling the Data Synchronization 4 3 1 Starting the Service When SpiraTeam is installed a Windows Service SpiraTeam Data Sync Service is installed along with the web application However to avoid wasting system resources this service is initially set to run manually To ensure continued synchronization of SpiraTeam with Bugzilla we recommend starting the service and setting its startup type to Automatic To make these changes open up the Windows Control Panel click on the Administrative Tools link and then choose the Services option Th
229. s for the OnTimeDataSync plug in entry Incident Component Priority Seventh Status Type From this screen you need to click on Priority Severity and Status in turn to configure their values OnTime doesn t support different defect types a Incident Status Click on the Status hyperlink under Incident Standard Fields to bring up the Incident status mapping configuration screen Artifact Type Incident Field Name Status 7 So hee ALUS Assigned Closed lt i Duplicate A lt a New Yes Open Not Reproducible 7 On Hold Open Reopen i Resolved A lt d io The table lists each of the incident statuses available in SpiraTeam and provides you with the ability to enter the matching OnTime defect status names for each one You can map multiple SpiraTeam fields to the same OnTime fields e g New and Open in SpiraTeam are both equivalent to Open in OnTime in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from OnTime gt SpiraTeam We recommend that you always point the New and Open statuses inside SpiraTeam to point to the Open status inside OnTime and make Open in SpiraTeam the Primary status of the two This is recommended so that as new incidents in SpiraTeam get synched over to OnTime they will get switched to the Open status in OnTime which will then be synched back to Open in SpiraTeam
230. s servername 9443 ccm gt Login this should be set to a valid login for your RTC installation The login needs to have permissions to create and view work items within RTC gt Password this should be set to the password of the login specified above gt Time Offset normally this should be set to zero but if you find that issues being changed in RTC are not being updated in SpiraTeam try increasing the value as this will tell the data synchronization plug in to add on the time offset in hours when comparing date time stamps Also if your RTC installation is running on a server set to a different time zone then you should add in the number of hours difference between the servers time zones here Auto Map Users this is not currently used and can be ignored Custom 01 this is not currently used and can be ignored Custom 02 this is not currently used and can be ignored Custom 03 this is not currently used and can be ignored Custom 04 this is not currently used and can be ignored Custom 05 this is not currently used and can be ignored VVV VV V 9 2 Configuring the Data Mapping Next you need to configure the data mapping between SpiraTeam and RTC This allows the various projects users incident statuses priorities severities and custom property values used in the two applications to be related to each other This is important as without a correct mapping there is no way for the integratio
231. s application is described in Appendix 1 and can be used instead of the server based DataSyncService 4 1 2 Configuring the Service To configure the integration service please open up the DataSyncService exe config file located in C Program Files SpiralTeam Bin with a text editor such as Notepad Once open it should look like lt xml version 1 0 encoding utf 8 gt COnriguraction gt lt configSections gt lt sectionGroup name applicationSettings type System Configuration ApplicationSettingsGroup System Version 2 0 0 0 Culture neutral PublicKeyToken b77a5c561934e089 gt lt section name Inflectra SpiraTest DataSyncService Properties Settings type System Configuration ClientSettingsSection System Version 2 0 0 0 Culture neutral PublickeyToken b77a5c561934e089 requirePermission false gt lt sectionGroup gt lt configSections gt lt applicationSettings gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt setting name PollingInterval serializeAs String gt lt value gt 600000 lt value gt lt setting gt lt setting name WebServiceUrl serializeAs String gt lt value gt http localhost SpiraTeam lt value gt lt setting gt lt setting name Login serializeAs String gt lt value gt readbl6ggs lt value gt lt setting gt lt setting name Password serializeAs String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name EventLogS
232. s below Spira URL http localhosty S piraT est e eel Connect Succeeded ae tti tst CiaS Succeeded x E A l 5 Successfully connected to the Server Settings Polling Interval 2 minutes Enable Trace Logging W Start Cancel Now you should complete the configuation by setting the Polling Interval how often the utility will synchronize data between Spira and the external system and whether Trace Logging is enabled useful when verifying your data mapping but will fill up the application log so leave unchecked for production use Then click the Update button to save your settings or Start to save your settings and start synchronization immediately Once the Options window closes the application will remain active in the system tray of your computer Start Synchronization Stop Synchronization Statuts Options Exit Ge i 6am You can then use the right click context menu to start synchronization stop synchronization view the status if synchronization is running or exit the application altogether During synchronization any errors will be logged to the Windows Application Event Log and you can use those logs to diagnose any issues connecting to the external bug tracker or any data mapping configuration changes that need to be made Legal Notices This publication is provided as is without warranty of any kind either express or implied including but not limited to the implied warranties
233. s to Yes so that SpiraTeam knows that you want to synchronize data for this project Once the project has been completed setting the value to No will stop data synchronization reducing network utilization Click Update to confirm these settings Once you have enabled the project for data synchronization you can now enter the other data mapping values outlined below Note Once you have successfully configured the project when creating a new project you should choose the option to Create Project from Existing Project rather than Use Default Template so that all the project mappings get copied across to the new project 5 2 2 Configuring the User Mapping To configure the mapping of users in the two systems you need to go to Administration gt Users gt View Edit Users which will bring up the list of users in the system Then click on the Edit button for a particular user that will be editing work items in TFS Add Edit User System Administrator Please review the information listed below and make any changes if necessary Once you have finished click Update Insert to confirm them First Name Middle Initial Last Name User Name Department Email Address administrator mycompany com Email Enabled System Administrator Active Locked Out No RSS Token C Enable RSS Feeds Project Membership Passwords amp Security Data Mapping MTE Data Sya M Y
234. se installation of SpiraTeam but instead are using a hosted subscription provided by Inflectra or a third party company you will not have access to the DataSyncService background service In such situations you should use the Desktop DataSync application instead This application is described in Appendix 1 and can be used instead of the server based DataSyncService 3 1 2 Configuring the Service To configure the integration service please open up the DataSyncService exe config file located in C Program Files SpiralTeam Bin with a text editor such as Notepad Once open it should look like lt xml version 1 0 encoding utf 8 gt lt conitiguration gt lt configSections gt lt sectionGroup name applicationSettings type System Configuration ApplicationSettingsGroup System Version 2 0 0 0 Culture neutral PublicKeyToken b77a5c561934e089 gt lt section name Inflectra SpiraTest DataSyncService Properties Settings type System Configuration ClientSettingsSection System Version 2 0 0 0 Culture neutral PublickeyToken b77a5c561934e089 requirePermission false gt lt sectionGroup gt lt configSections gt lt applicationSettings gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt setting name PollingInterval serializeAs String gt lt value gt 600000 lt value gt lt setting gt lt setting name WebServiceUrl serializeAs String gt lt value gt http localhost SpiraTeam lt value gt
235. setting gt lt setting name Login serializeAs String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name Password serializeAs String gt lt value gt Yredbleggs lt value gt lt setting gt lt setting name EventLogSource serializeAs String gt lt value gt SpiraTeam Data Sync Service lt value gt lt setting gt lt setting name TraceLogging serializeAs String gt lt value gt False lt value gt lt setting gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt applicationSettings gt lt Configuratlion gt The sections that need to be verified and possibly changed are marked in yellow above You need to check the following information gt The polling interval allows you to specify how frequently the data synchronization service will ask Spiraleam and the external system for new data updates The value is specified in milliseconds and we recommend a value no smaller than 5 minutes i e 300 000ms The larger the number the longer it will take for data to be synchronized but the lower the network and server overhead gt The base URL to your instance SpiraTeam It is typically of the form http lt server name gt SpiraTeam Make sure that when you enter this URL on a browser on the server itself the application login page appears gt A valid login name and password to your instance of SpiraTeam This user needs to be a member of the project s that wil
236. should the name of the ClearQuest master database In most installations this is simply called MASTR gt Login this should be set to a valid login for your ClearQuest installation The login needs to have permissions to create and view defects within ClearQuest gt Password this should be set to the password of the login specified above gt Time Offset normally this should be set to zero but if you find that issues being changed in ClearQuest are not being updated in SpiraTeam try increasing the value as this will tell the data synchronization plug in to add on the time offset in hours when comparing date time stamps Also if your ClearQuest installation is running on a server set to a different time zone then you should add in the number of hours difference between the servers time zones here gt Auto Map Users this is not currently used and can be ignored gt Custom 01 This should be set to the word True if you want to have the plugin restrict synchronization to only loading new incidents from SpiraTeam gt ClearQuest and updating existing items This is useful if you want to prevent existing issues in ClearQuest from being loaded into SpiraTeam Leave blank if you want the plugin to synchronize normally gt Custom 02 Sometimes you don t want all the incidents in SpiraTeam to be added to ClearQuest You can optionally enter a filter definition in this box to restrict the incidents that get sync
237. st Name loggs User Name fredbloggs System Administrator Active User OnTimeData Sync ID You will notice that below the Active flag for the user is a list of all the configured data synchronization plug ins In the text box next to the OnTime Data Sync plug in you need to enter the Login ID for this username in OnTime This will allow the data synchronization plug in to know which user in SpiraTeam match which equivalent user in OnTime Click Update once you ve entered the appropriate login name You should now repeat for the other users who will be active in both systems 12 2 3 Configuring the Release Mapping When the data synchronization service runs when it comes across a release iteration in SpiraTeam that it has not seen before it will create a corresponding Release in OnTime Similarly if it comes across a new Release in OnTime that it has not seen before it will create a new Release in SpiraTeam Therefore when using both systems together it is recommended that you only enter new Releases in one system and let the data synchronization service add them to the other system However you may start out with the situation where you already have pre existing Releases in both systems that you need to associate in the data mapping If you don t do this you may find that duplicates get created when you first enable the data synchronization service Therefore for any Releases Iterations that already exist in BOTH syst
238. st custom property under Incident Custom Properties to bring up the custom property mapping configuration screen For list custom properties there will be a textbox for both the custom field itself and a mapping table for each of the custom property values that need to be mapped Edit Custom Property Data Mapping Sample OnTime Project Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the OnTimeDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name OnTime Operating System External Key Qperating System Custom Value Mapping Windows 2000 Windows 2003 Windows NT Windows XP First you need to lookup the display name of the custom field in OnTime that matches this custom property in SpiraTeam This should be entered in the External Key field below the name of the custom property Next for each of the Property Values in the table in the lower half of the page you need to enter the full name of the custom field value as specified in OnTime c OnTime s Replication Procedures Field If you want new defects in OnTime to be loaded with the replication prodcedures standard text field populated then you will need to fill out this section You first need to create an incident custom property in Spiraleam of type TEXT
239. stom Value Mapping Approved Approved Investigate First you need to enter the full Reference Name of the TFS field as the External Key of the custom property This tells the data sync plug in that the custom property in SpiraTeam should be mapped to this specific field in TFS To see a list of fields and their reference names you can run the following SQL query against your TFS database SELECT Name ReferenceName FROM Fields ORDER BY Name We have included a list of fields in the Agile process template in section 5 5 of this guide as a helpful reference Next for each of the Property Values in the table in the lower half of the page you need to enter the name of the field values as they appear in TFS as the External Key 5 2 6 Configuring the Standard Task Field Mapping Now that the projects user releases and incident fields have been mapped correctly we need to configure the standard task fields To do this go to Administration gt System gt Data Synchronization and click on the View Project Mappings for the MsTfsDataSync plug in entry Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Requirement Importance Area Status Risk Test Case Pronty Incident Pnonty Area Severity Stac Status Release Task Prionty Status From this screen you need to click on Priorit
240. stom list property you also need to fill in the external key for each of the custom property values as well Name Notes External Key 40040 You need to lookup the ID of the custom field in ClearQuest that matches this custom property in SpiraTeam Once you have entered the id of the custom field click Update Note The ID can be found by looking at the URL inside ClearQuest when choosing to View Edit the Custom Field The URL will include the section id X where X is the numeric ID of the Custom Field inside ClearQuest b List Custom Properties Click on the hyperlink of the list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen For list custom properties there will be a textbox for both the custom field itself and a mapping table for each of the custom property values that need to be mapped Edit Custom Property Data Mapping Sample Application Two Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the ClearliuestDataSyne external key values forthe custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Hame RFesalution Fedsiel Savi p orks x ns i BLE NE Y Duplicate Duplicate Enhancement Request Enhancement Request Fixed Fixed Fixed Indirectly Fixed Indirect Functions as Designed Fu
241. sync plug in and can be left blank 10 2 Configuring the Data Mapping Next you need to configure the data mapping between Spiraleam and OnTime This allows the various projects users releases incident statuses priorities severities and custom property values used in the two applications to be related to each other This is important as without a correct mapping there is no way for the integration service to Know that an Open incident in SpiraTeam is the same as an Open defect in OnTime for example The following mapping information needs to be setup in SpiraTeam gt gt gt gt gt The mapping of the project identifiers for the projects that need to be synchronized The mapping of users in the system The mapping of releases in the system The mapping of the various standard fields in the system The mapping of the various custom properties in the system Each of these is explained in turn below 10 2 1 Configuring the Project Mapping From the data synchronization administration page you need to click on the View Project Mappings hyperlink next to the OnTime plug in name This will take you to the data mapping home page for the currently selected project OnTimeDataSync Project Data Mapping On Time Sample Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the OnTimeDataSync plug in you need to specify the key id of the project in th
242. t lt value gt SpiraTeam Data Sync Service lt value gt lt setting gt lt setting name TraceLogging serializeAs String gt lt value gt False lt value gt lt setting gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt applicationSettings gt lt contiquration gt The sections that need to be verified and possibly changed are marked in yellow above You need to check the following information gt The polling interval allows you to specify how frequently the data synchronization service will ask Spiraleam and the external system for new data updates The value is specified in milliseconds and we recommend a value no smaller than 5 minutes i e 300 000ms The larger the number the longer it will take for data to be synchronized but the lower the network and server overhead gt The base URL to your instance SpiraTeam It is typically of the form http lt server name gt SpiraTeam Make sure that when you enter this URL on a browser on the server itself the application login page appears gt Avvalid login name and password to your instance of SpiraTeam This user needs to be a member of the project s that will be synchronized with Redmine and needs to have at least Incident create modify view permissions and Release create modify view permissions in these projects The default Manager role would be an appropriate choice Once you have made these changes save the file and proceed to the next st
243. t Delete This screen lists all the plug ins already configured in the system Depending on whether you chose the option to include sample data in your installation or not you will see either an empty screen or a list of sample data synchronization plug ins If you already see an entry for JiraDataSync you should click on its Edit link If you don t see such an entry in the list please click on the Add button instead In either case you will be taken to the following screen where you can enter or modify the JIRA Data Synchronization plug in Edit Plug In JiraDataSync lt lt Back to Data Synchronization Home Please enter edit the following information for the plug in The exact information that needs to be entered is specific to each plug in and you should refer to the documentation for the plug in when entering changing it Name JiraDataSyne Description This plug in allows incidents in the system to be synchronized with the JIRA issue tracking system Connection Info http inflectrasvr01 rpc soap jirasoapservice v2 Login Password Time Offset Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 You need to fill out the following fields for the JIRA Plug in to operate correctly gt Name this needs to be set to JiraDataSync This needs to match the name of the plug in DLL assembly that was copied into the C Program Files SpiraTeam Bin folder minus the dll file extension If you
244. t Yes Enhancement Yes Incident Yes Ware in a a 4 Issue Yes j a Limitation Yes New Value No Risk Task j j ii ib aoa j Training Hl ts The table lists each of the incident types available in SpiraTeam and provides you with the ability to enter the matching JIRA issue type ID for each one You can map multiple SpiraTeam fields to the same JIRA fields e g Bug and Incident in SpiraTeam are both equivalent to Bug in JIRA in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from JIRA gt SpiraTeam The JIRA ID can be found by looking at the URL inside JIRA when choosing to View Edit the Issue Type The URL will include the section id X where X is the numeric ID of the Issue Type inside JIRA Issue Types Issue Types Issue Types Issue Type Schemes Name Operations Sub Tasks Bug Edit Delete A problem which impairs or prevents the functions of the product a Improvement Edit Delete An improvement or enhancement to an existing feature or task New Feature Edit Delete A new feature of the product which has yet to be developed Story Edit Delete Story Task Edit Delete A task that needs to be done A User Story Edit Delete Agile User Story Bug tracking and project tracking for software development powered by Atlassian JIRA v5 2 7 850 sha1 b2af0c8 Report a problem
245. t to the word True if you want to have the plugin restrict synchronization to only loading new incidents from SpiraTeam gt JIRA and updating existing items This is useful if you want to prevent existing issues in JIRA from being loaded into Spiraleam Leave blank if you want the plugin to synchronize normally Custom 04 This should be set to a comma separated list of IDs of any JIRA issue types that you want to be synchronized with SpiraTeam requirements instead of incidents If you leave this blank all JIRA issue types will be synchronized with incidents Custom 05 This should be set to the name of the JIRA issue link type that you want SpiraTeam incident associations to use If you leave this blank incident associations in SpiraTeam will not be imported into JIRA You can get the list of issue link types from the following screen in JIRA Issue Features Time Tracking Issue linking is currently ON Issue Linking To deactivate issue linking simply click below For the users you wish to be able to link issues ensure that they have the Link Issues permission for that particular project Related related to related to Edit Delete Note For most users we recommend leaving Custom 01 Custom 04 blank 2 2 Configuring the Data Mapping Next you need to configure the data mapping between SpiraTeam and JIRA This allows the various projects users releases incident types statuses priorities and custom property va
246. t will be synchronized with JIRA and needs to have at least Incident create modify view permissions and Release create modify view permissions in these projects Once you have made these changes save the file and proceed to the next stage 3 1 3 Configuring the Plug In The next step is to configure the plug in within SpiraTeam so that the system knows how to access the JIRA server To start the configuration please open up SpiraTeam in a web browser log in using a valid account that has System Administration level privileges and click on the System gt Data Synchronization administration option from the left hand navigation Data Synchronization Refresh SpiraTeam is able to communicate with a variety of external systems and applications using its background data synchronization service and library of available plug ins This page allows you to view add and modify the list of plug ins make changes to their configuration and verify the status of the most recent synchronization In addition you can force a particular plug in to perform a complete data synchronization by resetting its date of last sync BugzillaDataSync gt View Project Mappings Not Run gt Force Re Sync Edit Delete FogBugzDataSync gt View Project Mappings Not Run gt Force Re Syne Edit Delete JiraDataSync gt View Project Mappings Not Run gt Force Re Sync Edit Delete MsTfsDataSync gt View Project Mappings Not Run gt Force Re Sync Edi
247. table lists each of the incident severities available in SpiraTeam and provides you with the ability to enter the matching TFS severity value for each one To make this easier we recommend that inside the Administration gt Edit Incident Severities screen you first make any statuses not used in TFS inactive in SpiraTeam 5 2 5 Configuring the Incident Custom Property Mapping Now that the various SpiraTeam standard incident fields have been mapped correctly we need to configure the custom property mappings This is used for both custom properties in SpiraTeam that map to custom fields in TFS and also for custom properties in SpiraTeam that are used to map to standard fields in TFS e g Area that don t exist in SpiraTeam From the View Edit Project Data Mapping screen you need to click on the name of the Incident Custom Property that you want to add data mapping information for Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Requirement Importance Status Test Case Prionty Incident Release Task a TFS s Area Field First you need to go to Administration gt Edit Custom Lists and create a new custom list that contains all the different Areas that are being used in TFS Then you need to go to Administration gt Edit Custom Properties and add a new ist custom property onto the Incid
248. tatus Started Started Started Startup Type Aornatic Automatic Automatic Akomatic Manual Maral Lag On As Local System Local Systern Local System Local System Local System Local Service beat Spa Local System Local Systern Local Service Local Systern Local System Local Systerh Local Service Local Systert lasal C bam Siy TCP IP NetBIOS Helper Siy Telephony a Talaa Enables support For NetBIOS over TCP IP N Provides Telephany API TAPI support For p an beh been Caskhias amp emma i a be snme extended Standard Click on the SpiraTeam Data Sync Service entry and click on the link to start the service Then right click the service entry and choose the option to set the startup type to Automatic This will ensure that synchronization continues between SpiraTeam and OnTime after a reboot of the server 10 3 2 Using SpiraTeam with OnTime Now that the integration service has been configured and the service started initially any incidents created in SpiraTeam for the specified projects will be imported into OnTime and vice versa At this point we recommend opening the Windows Event Viewer and choosing the Application Log In this log any error messages raised by the SpiraTeam Data Sync Service will be displayed If you see any error messages at this point we recommend immediately stopping the SpiraTeam service and checking the various mapping entries If you cannot see any de
249. tead of the server based DataSyncService 9 1 2 Configuring the Service To configure the integration service please open up the DataSyncService exe config file located in C Program Files Spiraleam Bin with a text editor such as Notepad Once open it should look like lt xml version 1 0 encoding utf 8 gt lt CONLLOUraLLOn gt CONTIGSeCt10nSs gt lt sectionGroup name applicationSettings type System Configuration ApplicationSettingsGroup System Version 2 0 0 0 Culture neutral PublicKeyToken b77a5c561934e089 gt lt section name Inflectra SpiraTest DataSyncService Properties Settings type System Configuration ClientSettingsSection System Version 2 0 0 0 Culture neutral PublickeyToken b77a5c561934e089 requirePermission false gt lt sectionGroup gt lt configSections gt lt applicationSettings gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt setting name PollingInterval serializeAs String gt lt value gt 600000 lt value gt lt setting gt lt setting name WebServiceUrl serializeAs String gt lt value gt http localhost SpiraTeam lt value gt lt setting gt lt setting name Login serializeAs String gt lt value gt Yre dbl6ggs lt value gt lt setting gt lt setting name Password serializeAs String gt lt value gt Yredbl6ggs lt value gt lt setting gt lt setting name EventLogSource serializeAs String gt lt value gt SpiraTeam
250. then you need to change the name here to match gt Description this should be set to a description of the plug in This is an optional field that is used for documentation purposes and is not actually used by the system gt Connection Info this should the URL that you use to access your instance of FogBugz e g httos mycompany fogbugz com gt Login this should be set to a valid login to the FogBugz installation The login needs to have permissions to create and view cases and versions within FogBugz gt Password this should be set to the password of the login specified above gt Time Offset normally this should be set to zero but if you find that cases being changed in FogBugz are not being updated in SpiraTeam try increasing the value as this will tell the data synchronization plug in to add on the time offset in hours when comparing date time stamps Also if your FogBugz installation is running on a server set to a different time zone then you should add in the number of hours difference between the servers time zones here gt Auto Map Users this is not currently used by the FogBugz data sync plug in and can be ignored gt Custom 01 When connecting to FogBugz sometimes the connection gets dropped by the server without notifying the plug in This happens when using HTTP 1 1 Keep Alive connections If you set this property to False it will tell the plug in to not use HT TP keep alives when c
251. tionProcedures Severity OnTime Operating System Status OnTime Environment Type Release Task Priority Status From this screen you need to click on Priority Severity and Status in turn to configure their values OnTime doesn t support different defect types a Incident Status Click on the Status hyperlink under Incident Standard Fields to bring up the Incident status mapping configuration screen Field Value Active External Ke Assigned 7 Closed 5 Closed i Duplicate New r al Not Reproducible 7 i a Open Reopen Resolved The table lists each of the incident statuses available in SpiraTeam and provides you with the ability to enter the matching OnTime defect status names for each one You can map multiple SpiraTeam fields to the same OnTime fields e g New and Open in SpiraTeam are both equivalent to Open in OnTime in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from OnTime gt SpiraTeam We recommend that you always point the New and Open statuses inside SpiraTeam to point to the Open status inside OnTime and make Open in SpiraTeam the Primary status of the two This is recommended so that as new incidents in SpiraTeam get synched over to OnTime they will get switched to the Open status in OnTime which will then be synched back to Open in SpiraTeam That way you ll be able to
252. tom property in SpiraTeam should be mapped to built in Resolution field in JIRA Next for each of the Property Values in the table in the lower half of the page you need to enter the JIRA ID of the various Resolutions that are configured in JIRA The external ID can be found by looking at the URL inside JIRA which choosing to View Edit the resolution name description e JIRA s Environment Field If your instance of JIRA requires that all new issues are submitted with an Environment description specified then you will need to fill out this section You first need to create an incident custom property in Spiraleam of type TEXT that will be used to store the environment description within SpiraTeam Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping JIRA DEMO Project Change Project To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below Ii this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Environment External Key Envyironment Custom Value Mapping All you need to do on this screen is enter the word Environment in the External Key textbox and the data sync plug in will know that this custom property is mapped to the
253. ttings type System Configuration ClientSettingsSection System Version 2 0 0 0 Culture neutral PublickeyToken b77a5c561934e089 requirePermission false gt lt sectionGroup gt lt conrigsSections gt lt applicationSettings gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt setting name PollingInterval serializeAs String gt lt value gt 600000 lt value gt lt setting gt lt setting name WebServiceUrl serializeAs String gt lt value gt http localhost SpiraTeam lt value gt lt setting gt lt setting name Login serializeAs String gt lt value gt re dbl6ggs lt value gt lt setting gt lt setting name Password serializeAs String gt lt value gt readbl6ggs lt value gt lt setting gt lt setting name EventLogSource serializeAs String gt lt value gt SpiraTeam Data Sync Service lt value gt lt setting gt lt setting name TraceLogging serializeAs String gt lt value gt False lt value gt lt setting gt lt Inflectra SpiraTest DataSyncService Properties Settings gt lt applicationSettings gt x conf 19uraracn gt The sections that need to be verified and possibly changed are marked in yellow above You need to check the following information gt The polling interval allows you to specify how frequently the data synchronization service will ask SpiraTeam and the external system for new data updates The value is specified in milliseconds and
254. ty under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Sample Application One Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSyne external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well JIRA Key Jiralssuekey Hame External Key All you need to do on this screen is enter the word JiralssueKey in the External Key textbox and the data sync plug in will know that this custom property is mapped to the built in Issue Key field in JIRA Once you have updated the various mapping sections you are now ready to start the service 3 3 Enabling the Data Synchronization 3 3 1 Starting the Service When SpiraTeam is installed a Windows Service SpiraTeam Data Sync Service is installed along with the web application However to avoid wasting system resources this service is initially set to run manually To ensure continued synchronization of SpiraTeam with JIRA we recommend starting the service and setting its startup type to Automatic To make these changes open up the Windows Control Panel click on the Administrative Tools link and then choose the Services option This will bring up the Windows Service control panel ni Services
255. type to Automatic To make these changes open up the Windows Control Panel click on the Administrative Tools link and then choose the Services option This will bring up the Windows Service control panel niu Services Fle Action View Help Beoe AM gt Gy Services Local i Services Local SpiraTeam Data Sync Service Start the service Description Manages the data synchronization between SpiraTeam and other external systems Name Sy Secunty Accounts Manager By Security Center egy Server Sa Shell Hardware Detection Sia Simple Mail Transfer Protocol SMTP By Smart Card th SpiraTeam Data Syne Service By SQLAgentsSPIRA Sy SOLSERVERAGENT By SSOP Discovery Service Siy System Event Notification By System Restore Service Sf Task Scheduler Description Stores security information For local user acc Monitors system security settings and config Supports File print and named pipe sharing Provides notifications For AutoPlay hardware Transports etachronic mail across the network Manages access to smart cards read by this Enables cescovery of UPnP devices on your h Tracks system events such as Windows laga Performs system restore functions To stop Enables a user to configure and schedule au Status Started Started Started Startup Type Aornatic Automatic Automatic Akomatic Manual Maral Lag On As Local System Local Systern Local System Local System Local S
256. ues in the table in the lower half of the page you need to enter the JIRA ID of the various Resolutions that are configured in JIRA The external ID can be found by looking at the URL inside JIRA which choosing to View Edit the resolution name description e JIRA s Environment Field If your instance of JIRA requires that all new issues are submitted with an Environment description specified then you will need to fill out this section You first need to create an incident custom property in Spiraleam of type TEXT that will be used to store the environment description within Spiraleam Then click on the hyperlink of this new list custom property under Incident Custom Properties to bring up the custom property mapping configuration screen Edit Custom Property Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Environment External Key Enyironment All you need to do on this screen is enter the word Environment in the External Key textbox and the data sync plug in will know that this custom property is mapped to the built in Environment field in JIRA f JIRA s Security Level Field JIRA 4 x Plug In Only I
257. ug In The next step is to configure the plug in within SpiraTeam so that the system knows how to access the Bugzilla server To start the configuration please open up SpiraTeam in a web browser log in using a valid account that has System Administration level privileges and click on the System gt Data Synchronization administration option from the left hand navigation Data Synchronization Refresh SpiraTeam is able to communicate with a variety of external systems and applications using its background data synchronization service and library of available plug ins This page allows you to view add and modify the list of plug ins make changes to their configuration and verify the status of the most recent synchronization In addition you can force a particular plug in to perform a complete data synchronization by resetting its date of last sync BugzillaDataSync gt View Project Mappings l Not Run gt Force Re Sync Edit Delete FogBugzDataSync gt View Project Mappings Not Run gt Force Re Syne Edit Delete JiraDataSync gt View Project Mappings Not Run gt Force Re Sync Edit Delete MsTfsDataSync gt View Project Mappings Not Run gt Force Re Sync Edit Delete This screen lists all the plug ins already configured in the system Depending on whether you chose the option to include sample data in your installation or not you will see either an empty screen or a list of sample data synchronization plug ins
258. unning of the test it will now be populated across into Bugzilla as a bug It will be populated with the information captured in SpiraTeam gt At this point the incident should not be acted upon inside SpiraTeam and all data changes to the issue should be made inside Bugzilla To enforce this you can modify the workflows set up in SpiraTeam so that the various fields are marked as inactive for all the incident statuses other than the New status This will allow someone to submit an incident in SpiraTeam but will prevent them making changes in conflict with Bugzilla after that point As the issue progresses through the Bugzilla workflow changes to the status priority severity and resolution will be updated automatically in SpiraTeam In essence SpiraTeam acts as a read only viewer of these incidents gt If you are using the plugin for Bugzilla 4 x changes to the hardware operating system and component will also be synchronized back into SpiraTeam In addition any comments added to the bug in Bugzilla 4 x will get added to the corresponding incident in SpiraTeam You are now able to perform test coverage and incident reporting inside SpiraTeam using the test cases managed by Spiraleam and the incidents managed on behalf of SpiraTeam inside Bugzilla 5 Using SpiraTest with MS TFS This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with the work item tr
259. upport inflectra com who will help you troubleshoot the problem To use SpiraTeam with Mantis on an ongoing basis we recommend the following general processes be followed gt When running tests in SpiraTest or SpiraTeam defects found should be logged through the Test Execution Wizard as normal gt Developers using Mantis can log new defects into either SpiraTeam or Mantis In either case they will get loaded into the other system gt Once created in one of the systems and successfully replicated to the other system the incident should not be modified again inside SpiraTeam Since Mantis is considered the master system for incidents issues all data changes to the issue should be made inside Mantis To enforce this you should modify the workflows set up in SpiraTeam so that the various fields are marked as inactive for all the incident statuses other than the New status This will allow someone to submit an incident in SpiraTeam but will prevent them from making changes in conflict with Mantis after that point gt As the issue progresses in Mantis changes to the type of issue changes to its status priority description and resolution will be updated automatically in SpiraTeam In essence SpiraTeam acts as a read only viewer of these incidents gt You are now able to perform test coverage and incident reporting inside SpiraTeam using the test cases managed by SpiraTeam and the incidents managed on behalf of SpiraTeam
260. ustom properties there will be no values listed in the lower half of the screen Edit Custom Property Data Mapping JIRA DEMO Project Ch lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below lf this is a custom list property you also need to fill in the external key for each of the custom property values as well Name Free Text Field External Key 79000 You need to lookup the ID of the custom field in JIRA that matches this custom property in SpiraTeam Once you have entered the id of the custom field click Update The ID can be found by looking at the URL inside JIRA when choosing to View Edit the Custom Field The URL will include the section id X where X is the numeric ID of the Custom Field inside JIRA Fields q Custom Fields Custom Fields sp Add Custom Field i Find More Custom Fields Field Configurations i d Name lype Available Context s Screens Field Configuration Custom Date Date Picker Issue type s Default Screen Global all issues e Resolve Issue Screen Workflow Screen Free Text Field Free Text Field unlimited text Issue type s Default Screen This is a free text field Global all issues Multi Select Field Multi Select Issue type s Default Screen This is a multi select field Global all issues Single Select List Select List Issue type s Default Screen Single Se
261. vailable in TFS for data mapping when using the TFS agile process template Arealevel sf Sytem AreaLevelt Arealevel4 sf Syytem AreaLevel4 Activated Date Microsoft VSTS Common ActivatedDate I System Local Data Source _ Microsoft VSTS TCM LocalDataSource WEF_BD66C4E18FB54884A18B2299E91AD WEF_BD66C4E18FB54884A18B2299E91ADE1B_ Syste E1B Extension Marker m ExtensionMarker WEF_BD66C4E18FB54884A18B2299E91AD WEF_BD66C4E18FB54884A18B2299E91ADE1B_ Kanba E1B Kanban Column n Column For a full list of the available TFS fields in the different process templates please refer to http msdn microsoft com en us library vstudio dd997792 aspx 6 Using SpiraTest with FogBugz This section outlines how to use SpiraTest SpiraPlan or SpiraTeam hereafter referred to as SpiraTeam in conjunction with the FogBugz issue bug tracking system The built in integration service allows the quality assurance team to manage their requirements and test cases in Spiraleam execute test runs in SpiraTest and then have the new incidents generated during the run be automatically loaded into FogBugz Once the incidents are loaded into FogBugz as cases the development team can then manage the lifecycle of these cases in FogBugz and have the status changes in FogBugz be reflected back in Spiraleam In addition any cases logged into FogBugz will get imported into SpiraTeam so that they can be linked to test cases and requirements 6 1 Con
262. vigation Data Synchronization Refresh SpiraTeam is able to communicate with a variety of external systems and applications using its background data synchronization service and library of available plug ins This page allows you to view add and modify the list of plug ins make changes to their configuration and verify the status of the most recent synchronization In addition you can force a particular plug in to perform a complete data synchronization by resetting its date of last sync JiraDataSync gt View Project Mappings 4 24 2013 10 30 19 PM Success gt Force Re Sync Edit Delete View Errors This screen lists all the plug ins already configured in the system Depending on whether you chose the option to include sample data in your installation or not you will see either an empty screen or a list of sample data synchronization plug ins If you already see an entry for JiraDataSync you should click on its Edit link If you don t see such an entry in the list please click on the Add button instead In either case you will be taken to the following screen where you can enter or modify the JIRA Data Synchronization plug in Edit Plug In JiraDataSync lt lt Back to Data Synchronization Home Please enter edit the following information for the plug in The exact information that needs to be entered is specific to each plug in and you should refer to the documentation for the plug in when entering changing it
263. we recommend a value no smaller than 5 minutes i e 300 000ms The larger the number the longer it will take for data to be synchronized but the lower the network and server overhead gt The base URL to your instance of SpiraTeam It is typically of the form http lt server name gt SpiraTeam Make sure that when you enter this URL on a browser on the server itself the application login page appears gt Avvalid login name and password to your instance of SpiraTeam This user needs to be a member of the project s that will be synchronized with TFS and needs to have at least Incident create modify view permissions and Release create modify view permissions in these projects Once you have made these changes save the file and proceed to the next stage 5 1 3 Configuring the Plug In The next step is to configure the plug in within SpiraTeam so that the system knows how to access the TFS server To start the configuration please open up SpiraTeam in a web browser log in using a valid account that has System Administration level privileges and click on the System gt Data Synchronization administration option from the left hand navigation Data Synchronization Refresh SpiraTeam is able to communicate with a variety of external systems and applications using its background data synchronization service and library of available plug ins This page allows you to view add and modify the list of plug ins make changes to their co
264. ws incidents in the system to be synchronized with the JIRA issue tracking system Connection Info http inflectrasvr01 rpc soap jirasoapservice v2 Login edbloggs Password Time Offset Custom 01 Custom 02 Custom 03 Custom 04 Custom 05 On this screen you need to enter the ID of the custom field that you re using to store severities in JIRA and populate the Custom 01 property with this value see above Note The ID can be found by looking at the URL inside JIRA when choosing to View Edit the Custom Field The URL will include the section id X where X is the numeric ID of the Custom Field inside JIRA 3 2 5 Configuring the Custom Property Mapping Now that the various SpiraTeam standard fields have been mapped correctly we need to configure the custom property mappings This is used for both custom properties in SpiraTeam that map to custom fields in JIRA and also for custom properties in SpiraTeam that are used to map to standard fields in JIRA Component Environment Resolution and SecurityLevel that don t exist in SpiraTeam From the View Edit Project Data Mapping screen you need to click on the name of the Incident Custom Property that you want to add data mapping information for We will consider the four different types of mapping that you might want to enter View Edit Project Data Mapping Library Information System Change Project lt lt Back to Data Synchronization Home To configure this
265. y and Status in turn to configure their values a Task Status Click on the Status hyperlink under Task Standard Fields to bring up the Task status mapping configuration screen Edit Standard Field Data Mapping TFS Test Project 1 Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the MsTitsDataSync plug in next to each Spiraleam value Field Value Active External Key 9 Primary Blocked Yes Removed Yes T Completed Yes Defered Yes o In Progress Active Yes Not Started New Yes The table lists each of the task statuses available in SpiraTeam and provides you with the ability to enter the matching TFS work item State for each one Unlike the mapping for incidents see above SpiraTeam does not track the reason codes associated with the tasks in MS TFS so you only need to map the State names from TFS with the task status names You can map multiple SpiraTeam fields to the same TFS fields e g Blocked Completed and Deferred in Spiraleam are all equivalent to State Closed in TFS in which case only one of the values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from TFS gt SpiraTeam b Task Priority TFS 2012 Plugin Only Click on the Priority hyperlink under Task Standard Fields to bring up the Task Priority mapping configuration screen 1 Critical Yes
266. y mapping configuration screen For list custom properties there will be a textbox for both the custom field itself and a mapping table for each of the custom property values that need to be mapped Edit Custom Property Data Mapping OnTime Sample Project Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the OnTimeDataSync external key values for the custom property below If this is a custom list property you also need to fill in the external key for each of the custom property values as well Artifact Type Incident Name OS MultiList External Key Qperating System Custom Value Mapping Linux 3 inux Mac OS X 5 Mac OS X Windows 7 3 as f Windows 8 5 Windows 8 First you need to lookup the display name of the custom field in OnTime that matches this custom property in SpiraTeam This should be entered in the External Key field below the name of the custom property Next for each of the Property Values in the table in the lower half of the page you need to enter the full name of the custom field value as specified in OnTime Once you have updated the various mapping sections you are now ready to start the service 10 3 Enabling the Data Synchronization 10 3 1 Starting the Service When SpiraTeam is installed a Windows Service SpiraTeam Data Sync Service is installed along with the web application However to avoid wasting s
267. you need to click on the name of the Incident Custom Property that you want to add data mapping information for We will consider the two different types of mapping that you might want to enter ClearQuestDatasync Project Data Mapping Sample Application Two Change Project lt lt Back to Data Synchronization Home To configure this project for data mapping with the ClearQuestDataSyne plug in you need to specify the key id of the project in the external system and then click on the links below to actually configure the different flelds that need to be mapped for the synchronization ta operate Project Name Sample Application Two External Key SAMPL Artifact Field Mapping Please click on each of the links below to configure the field level data mapping for each of the types of artifact that you will be synchronizing in this project Incident Product Resolution Release Task Priority Status a Text Custom Properties Click on the hyperlink of the text custom property under Incident Custom Properties to bring up the custom property mapping configuration screen For text custom properties there will be no values listed in the lower half of the screen Edit Custom Property Data Mapping Library Information System Change Project lt lt Back to Project Mappings To configure the data mappings for this custom property please fill in the JiraDataSync external key values for the custom property below If this is a cu
268. you will be synchronizing in this project Requirement Importance otatus Test Case Priority Incident Priority Severity Status Type Release Task Priority Status From this screen you need to click on Priority Type and Status in turn to configure their values a Incident Status Click on the Status hyperlink under Incident Standard Fields to bring up the Incident status mapping configuration screen Edit Standard Field Data Mapping Redmine Demo Project Change Project lt lt Back to Project Mappings To configure the data mappings for this field please fill in the external key values for the RedmineDataSync plug in next to each Spiraleam value Assigned Closed j wa a Duplicate New mm mm P ak i q lt Not Reproducible Open Reopen Resolved tA The table lists each of the incident statuses available in SpiraTeam and provides you with the ability to enter the matching Redmine bug status ID for each one You can map multiple SpiraTeam fields to the same Redmine fields e g Open and Assigned in SpiraTeam are both equivalent to In Progress ID 2 in Redmine in which case only one of the two values can be listed as Primary Yes as that s the value that s used on the reverse synchronization from Redmine gt SpiraTeam b Incident Priority Click on the Priority hyperlink under Incident Standard Fields to bring up the Incident Priority mapping configu
269. ystem Local Service beat Spa Local System Local Systern Local Service Local Systern Local System Local Systerh Local Service Local Systert lasal C bam Siy TCP IP NetBIOS Helper Siy Telephony a Talaa Enables support For NetBIOS over TCP IP N Provides Telephany API TAPI support For p an beh been Caskhias amp emma i a be snme extended Standard Click on the SpiraTeam Data Sync Service entry and click on the link to start the service Then right click the service entry and choose the option to set the startup type to Automatic This will ensure that synchronization continues between SpiraTeam and ClearQuest after a reboot of the server 8 3 2 Using SpiraTeam with ClearQuest Now that the integration service has been configured and the service started initially any incidents created in SpiraTeam for the specified projects will be imported into ClearQuest and any existing defects in ClearQuest will get loaded into SpiraTeam At this point we recommend opening the Windows Event Viewer and choosing the Application Log In this log any error messages raised by the SpiraTeam Data Sync Service will be displayed If you see any error messages at this point we recommend immediately stopping the SpiraTeam service and checking the various mapping entries If you cannot see any issues with the mapping information we recommend sending a copy of the event log message s to Inflectra customer servic
270. ystem resources this service is initially set to run manually To ensure continued synchronization of SpiraTeam with OnTime we recommend starting the service and setting its startup type to Automatic To make these changes open up the Windows Control Panel click on the Administrative Tools link and then choose the Services option This will bring up the Windows Service control panel niu Services Fle Action View Help Beoe AM gt Gy Services Local i Services Local SpiraTeam Data Sync Service Start the service Description Manages the data synchronization between SpiraTeam and other external systems Name Sy Secunty Accounts Manager By Security Center egy Server Sa Shell Hardware Detection Sia Simple Mail Transfer Protocol SMTP By Smart Card th SpiraTeam Data Syne Service By SQLAgentsSPIRA Sy SOLSERVERAGENT By SSOP Discovery Service Siy System Event Notification By System Restore Service Sf Task Scheduler Description Stores security information For local user acc Monitors system security settings and config Supports File print and named pipe sharing Provides notifications For AutoPlay hardware Transports etachronic mail across the network Manages access to smart cards read by this Enables cescovery of UPnP devices on your h Tracks system events such as Windows laga Performs system restore functions To stop Enables a user to configure and schedule au S

Download Pdf Manuals

Related Search

Related Contents

MANUAL BEAUTY DERMO REV.05  AMS-224EN / IP-420 取扱説明書（日本語）  RayCam Usermanual - Dexcowin the leader in Portable Handheld X  DINION capture 5000 IP  sELEZIONE POMPE CENTRIFUGHE  

Copyright © All rights reserved. Failed to retrieve file