fbpx
Application Administration

Managing OAuth Consumers

Enterprise Tester uses OAuth to securely share data from Enterprise Tester with other applications including Jira and Confluence. OAuth is used to share Portlets from the Enterprise Tester dashboards with dashboards in JIRA and Confluence.

Configuring OAuth for a Jira / Confluence Consumer

From the Admin tab, double-click on OAuth Consumers to view all existing consumers. Alternatively, you can right-click on OAuth Consumers and select View Consumers.

To add a Consumer such as Jira or Confluence:

  1. Click on Add from the tool bar.
  2. The Edit Consumer screen will open.
  3. For Jira and Confluence the fields that are required to be completed are:

    a. Name
    b. Consumer Key
    c. Public Key

    You can find these details from the Jira or Confluence Consumer Information screen in your instance of Jira or Confluence, which can be found in the following locations:

    http://servername/JIRA/plugins/servlet/oauth/view-consumer-info
    http://servername/confluence/plugins/servlet/oauth/view-consumer-info

    An example of the Jira Consumer Information screen is displayed below:

  4. Once you have added and saved your Consumer information in Enterprise Tester, it will now accept connections from the Jira / Confluence server. All connections can be managed from this screen.

To add gadgets from Enterprise Tester in Jira or Confluence, please refer to the articles Alternative method to add Gadgets to Confluence and Alternative method to add Gadgets to Jira.

Application Administration

Notifications for Jira Synchronization Failures

Enterprise Tester supports both in-tray and e-mail notifications if the synchronization between Enterprise Tester and Jira fails at a project level.

To configure notifications for this:

1) Ensure you have the Resources > External Links permission.

2) Go into your ‘My Profile’ screen.

3) In the Notifications Section of the My Profile screen, select the ‘Sync Failures’ Event Type.

4) Ensure ‘Activate Tray Notifications’ and ‘Activate E-Mail Notifications’ are selected as required.

 

5) If you have Activate Tray Notifications selected, you can access notifications by clicking on the notification icon next to your username in the top right-hand corner of the screen.

If you have a Mail Server configured and Activate E-Mail Notifications selected, you will receive an e-mail.

Both in-tray and e-mail notifications contain a link that will take you directly to the failed Jira Synchronization for review.

Application Administration

Alternative method to add Gadgets to Jira

Gadget subscriptions in Jira and Confluence are recommended when adding Enterprise Tester gadgets to Jira and Confluence. However, there are alternative methods available:

This feature is not compatible with On Demand instances of Jira and Confluence.

  1. To add Jira Gadgets login to your instance of Jira and on the dashboard you wish to add the portlet, click on the “+ Add Gadget” button.
  2. From the Gadget Directory, click on “Add Gadget to Directory” and then paste the URL you have already copied from the clipboard and click ‘Save’.
  3. The Enterprise Tester gadget should now be available in the list of gadgets. Now click the “Add it now” button to add this new gadget to your dashboard.
  4.                    If you used Shared Authorization, the gadget will now display on your dashboard.
  5. If you used Individual authorization, the gadget should now display on your Jira dashboard but will not be authorized. Click on the “Click here to approve access now” link.

    If you are currently logged into Enterprise Tester the authorization screen will appear.  If you are not logged into Enterprise Tester you will need to log in first, then the authorization screen will appear.

  6. Clicking Allow or Deny here will close the window and refresh the gadget – if you clicked Deny an error will be displayed in the JIRA gadget indicating access has been denied, if you clicked Allow you should see the gadget in Jira refresh to display the correct content.

The gadget will now display the portlet content from Enterprise Tester within Jira.

Application Administration

Alternative methods of adding gadgets to Jira and Confluence

Gadget subscriptions in Jira and Confluence are recommended when adding Enterprise Tester gadgets to Jira and Confluence. However, there are alternative methods available:

Note

This feature is not compatible with On Demand instances of Jira and Confluence.

 

  1. Create your dashboard and gadgets in Enterprise Tester as required.
  2. In the gadget you wish to share, click the drawing pin icon in the portlet title bar.

  3. The gadget URL dialog appears.
  4. Select the relevant authorization method as per below:

    Note

    For Jira 6.3+ you must use Shared Authorization.

     

Shared Authorization

The option pre-authorizes the gadget and will display for all users on the Jira Dashboard or Confluence page.

Individual Authorization

  • Select the Individual Authorization tab.
  • click on Copy to clipboard to copy the URL.
  • If you choose the Individual Authorization, when you add the gadget to Jira or Confluence all other users will need to authorize the gadget to view it.

  • To add the gadget to JIRA, follow the help topic Alternative method to add Gadgets to JIRA.
  • To add the gadget to Confluence, follow the help topic Alternative method to add Gadgets to Confluence.
  • Access can also be revoked from this screen or from the User menu, select Manage OAuth Tokens.

Application Administration

Adding Gadgets to Jira Dashboards

Enterprise Tester supports the ability to add dashboard gadgets to Jira, providing the ability to share information from Enterprise Tester with the wider organization.

Jira can subscribe to Enterprise Tester gadgets at Organisation level or for a specific Dashboard.

This feature is not compatible with On Demand instances of Jira and Confluence.

  1. Create your dashboard and gadgets in Enterprise Tester as required.
  2. If sharing is required at an Organisation level;

    – Navigate to the Edit Organisation Page in the Enterprise Tester Admin tab.

    – Copy the Organisation Subscription link.

     

    If sharing is required at a Dashboard level;

    – Navigate to the Manage Dashboards via the Dashboard menu.

    – Highlight the dashboard to be shared.

    – Click the Copy gadget URL to clipboard button on the toolbar.

  3. To add an Enterprise Tester subscription Jira, login to your instance of Jira. On the dashboard you wish to add the portlets to, click on the + Add Gadget button.

  4. From the Add a Gadget screen click on the Manage Gadgets Link

  5. Click on the Subscriptions tab

  6. Paste the Organisation or Dashboard URL as required and click Add subscription Administration functions are now complete.

  7. General users in Enterprise Tester can now go to the gadget that needs to be shared, click the drawing pin icon in the gadget title bar.
  8. Select the Shared Authorization tab and click on the Share button.

  9. The Enterprise Tester gadget will now be available in the list of gadgets in the Other category in Jira (you may have to select “Load All” first).
    Click the Add Gadget button to add the gadget to your Jira dashboard.

Application Administration

Creating Jira sync for incidents

Create an Incident Link
This User Guide has been created to show how to create and set up synchronization between Jira and Enterprise Tester for Incidents


1) Go to Resources tab in the menu
1) Double click on Project Links
2) Find the Project that you want to be able to synchronize Incidents to Jira
3) Expand the Project
4) Right-click and select Add New Project Link


1) Enter a name for the External System Link
2) Select Incidents from the Source drop-down list. This is the entity type you wish to synchronize.

External Link Details


1) Select Incidents in the Source drop-down list
2) Select the Enterprise Tester Project you want the Incidents to be synchronized from in the Project drop-down list under Source field.
3) Select the External JIRA System to synchronize to in the Destinations drop-down list
4) Select the Project in JIRA that you want to synchronize the Incidents to in the Project drop-down list under the Destination field.

ET Configuration tab

  • There are no options in this section for incident synchronization links because Enterprise Tester will synchronize all incidents created in Enterprise Tester for this project with the Jira project configured.
  • If you have more than one Jira project configured to synchronize with this project, you can select which project you wish to synchronize with on the incident screen.
  • You can also choose to synchronize Enterprise Tester incidents with more than one Jira project provided that you have set up multiple project links.

External System Configuration tab


You may also want to synchronize Incidents from Jira to Enterprise Tester. This is so that any incidents logged in Jira by users that do not have access to Enterprise Tester, i.e. developers will be synchronized to Enterprise Tester.
The first thing you need to do is click on Refresh Lookups button.
Refresh Lookups allows Enterprise Tester to pull in static information from Jira. Static information can consist of items like Custom Field values or Workflow configurations.

Refresh Lookups


Click on the Refresh Now button

Refresh Status


Once you have clicked on the Refresh Now button you will see the Refresh Status now has an elapsed time.
The time progresses until the Refresh Lookups is complete.

Refresh Lookups Completed


Once the Refresh Status changes back to Idle the Refresh Lookups is completed.
Last refresh duration: will have how long the Refresh Lookups took.
Select the Close button.

Save External System Configuration


Once the Refresh Lookups is completed and closed the External Configuration tab is displayed. Click on the Save button

Incident Types


You can select the Incident Types you want to synchronize from Jira to Enterprise Tester by selecting the Types drop-down list.
Note: This will usually be Bug, but you may have some other user-defined Types in Jira.

  • This will show all the available Incident Types in Jira.
  • You can select multiple Incident Types.
  • If Types are not filtered all Incident Types will be synchronized from Jira to Enterprise Tester

Incident Statuses

  • You can select the Incident Statuses you want to synchronize from Jira to Enterprise Tester by selecting the Statuses drop-down list.
  • This will show all the available Incident Statuses in Jira.
  • You can select multiple Incident Statuses.
  • If Statuses are not filtered all Incident Statuses will be synchronized from Jira to Enterprise Tester


Incident Priorities

  • You can select the Incident Priorities you want to synchronize from Jira to Enterprise Tester by selecting the Priorities drop-down list.
  • This will show all the available Incident Priorities in Jira.
  • You can select multiple Incident Priorities.
  • If Priorities are not filtered all Incident Priorities will be synchronized from Jira to Enterprise Tester



All Incident Priorities will be synchronized, as there is no filter.

JQL Queries


You can use a JQL query from Jira to filter what Incidents are synchronized from Jira to Enterprise Tester.
Note: It is recommended that you run the JQL query in Jira first to ensure the filter returns the results you are expecting.

Jira Project


Displayed is the project that will be synchronized with Enterprise Tester.
For this example, it is showing all requirements and bugs that will be in Release 7.0.
To pull Bugs only into Enterprise Tester you could use the following JQL:
Type = Bug
Once you have checked your JQL in Jira and are satisfied with the results returned, copy the JQL to Enterprise Tester 

You do not have to add the Project Name in the JQL as it is already connecting to the Jira Project

Versions and Components


You can also filter on Affected Versions, Fixed Versions, and Components.

Allow Unassigned Issues


You can synchronize Incidents from Jira where there is no assignee.
Your Jira project must be configured to allow “unassigned” issues.
You need to edit the field configuration in Enterprise Tester and set the AssignedTo field as optional. See here for guide

Mappings


This screen displays two tabs for outlining and configuring the steps undertaken when synchronization is initiated.
• One tab for mapping fields from Enterprise Tester to the external system (Jira).
• One tab for mapping fields from the external system (Jira) to Enterprise Tester
It defaults to ET to External System tab.

Map Fields (ET to External System)


The Configured column for Map Fields is set to False.
Double click on the Map Fields row

Configure Field Mappings

  • From the Configure Fields Mappings screen, several configurations are automatically created consisting of Copy Field type mappings and direct Map field type mappings.
  • The Copy Field type mappings are already configured and the value will be copied from Enterprise Tester to Jira on Synchronization.
  • The Map field type mappings require the field values to be mapped. You can see under the column Configured = False that the value for these fields have not yet been mapped.

The fields that you are required to Map are the following:
Map Field — Map from ET: Type to External System: Type
Map Field — Map from ET: Priority to External System: Priority
Map Field — Map from ET: Status to External System: Status
Map Field — Map from ET: Resolution to External System: Resolution
The other Map fields are optional
Double click on Map Field — Map from ET: Type to External System: Type row

Map field values for Type


Map values pop up screen is displayed.
The values on the left-hand side are Enterprise Tester fields and the values on the right-hand side with drop-down lists are Jira values.
Map the values you want for Type and select Save Changes button.
For Incidents, the type will generally be Bug.

Configure field mappings


Configured status for Map Field — Map from ET: Type to External System: Type row is now true
Double click on Map Field — Map from ET: Priority to External System: Priority row

Map field values for Priority


Map values pop up screen is displayed.
The values on the left-hand side are Enterprise Tester fields and the values on the right-hand side with drop-down lists are Jira values.
Map the values you want for Priority and select Save Changes button 

Configured status for Map Field — Map from ET: Priority to External System: Priority row is now true.
Double click on Map Field — Map from ET: Status to External System: Status row

Map Status values


The values on the left-hand side are Enterprise Tester fields and the values on the right-hand side with drop-down lists are Jira values.
Map the values you want for Status and select Save Changes button 

Configured status for Map Field — Map from ET: Status to External System: Status row is now true.
Double click on Map Field — Map from ET: Resolution to External System: Resolution row

Map Resolution values


The values on the left-hand side are Enterprise Tester fields and the values on the right-hand side with drop-down lists are Jira values.
Map the values you want for Status and select Save Changes button

Field Mappings Completed


All the required field mappings are now configured in ET to External System tab.
The required field mapping have a status of true. 

External System to ET tab


Select External System to ET tab

Field Mappings from External System to ET


You do not need to edit the mappings from Jira to Enterprise Tester as they are already complete. However, you can edit them if required.
You can also add Custom fields to synchronize.

Scheduling Requirement Synchronisation


Now that your configuration and field mappings are complete you are ready to synchronize.
By default, for incidents, the following schedules are pre-configured.

  • Periodic schedule occurring every 15 minutes, from Jira which will update all incidents that have been updated since the last synchronisation. This is conditional on having been previously synchronised.
  • On change, synchronization is in the direction of Enterprise Tester to Jira. A synchronization of all incidents added or updated in Enterprise Tester since last synchronized will be initiated at the time a change occurs to an incident in Enterprise Tester. This synchronization only updates Jira with the changes made in Enterprise Tester.

Add a New Schedule


Click on the Add icon in the tool bar
New Schedule pop up will be displayed

Select Type of Synchronisation


Select the schedule you want to add from the Type drop down list
If this is the first synchronisation for the projects between Jira and Enterprise Tester select Ad-hoc

Enter Schedule Type Details


Enter the details for the Schedule type selected.
Select the Save button

Schedules


Once you have configured your synchronisation frequency, a summary of the configured synchronisation schedules is available.
You can see the time of the Last Run, the Next Run (if applicable), whether the schedule is enabled or not and the current Synchronisation Status.
You can use the tool bar to add a new scheduled synchronisation, delete an existing configuration, enable or disable an existing schedule, configure an existing schedule or manually initiate a synchronisation.

Application Administration

Activity Streams on Jira Dashboard

Configuring Activity Streams to display on Jira Dashboards

When integrating with Jira 5 and above, you can configure events from Enterprise Tester to display on the Jira Activity Stream Gadget on Jira Dashboards.  The following provides the step to create and configure an Enterprise Tester activity stream that can be displayed on your Jira dashboard. For information on how to configure activity streams for your Enterprise Tester dashboard, please refer to  Activity Stream.

  1. From the Admin tab, click to expand the ‘Extensions’ folder.
  2. Double click on ‘Activity Stream Synchronizers’ to load the Activity Stream configuration screen.
  3. The Activity Stream Configuration screen will display all activity streams that have previously been configured. The details of each synchronizer will include the following:
    • Title
    • Type
    • Description
    • Enabled status
    • Date and time of the last synchronization
    • Status of the last synchronization
    • Comments regarding the last synchronization
  4. To add a new activity stream, click on the ‘Add’ button on the toolbar.

The New Activity Stream synchronizer screen will appear. Here you can enter the details of the activity stream you wish to add:

    • Enabled will automatically be selected.  This will enable the activity stream to be synchronized with Jira
    • Type – specify the type of defect tracker to add the activity stream to.  Currently, only Jira 5 and above are supported.
    • Jira instance – specify the Jira instance to add the activity stream to.
    • Stream Title – This is the activity stream title that will appear on the Jira activity stream gadget for selection.
    • Project – Select the project(s) the activity stream should post events from. When no project is select, events from all projects will be posted.
    • Entity Type – Select the entity type(s) the activity stream should post events from.  When no entity type is selected, events from all entities will be posted.
    • Event Type – Select the event(s) the activity stream should post events for.  When no event type is selected, all events will be posted.

A summary of the activity stream event configuration is shown in the ‘Filter Summary’ section.

Click ‘Save and Close’.  The activity stream will now be listed on the Activity Stream Synchronizers summary screen.

In Jira, when an activity stream is added to your project or system dashboard, users can now select to add the Enterprise Tester activity streams that have been configured.

 Jira Activity Stream Configuration ET Activity Stream events displaying on the Jira Dashboard
Application Administration

Allow Unassigned Issues to be synchronized with Jira

Enterprise Tester can now synchronize Requirements or Incidents to Jira where there is no assignee, the prerequisites to this are:

  • Integration must be with Jira 6.4.1 or later.
  • Your Jirra project must be configured to allow “unassigned” issues.
  • You need to edit the field configuration in Enterprise Tester and set the AssignedTo field as optional.
  • Configure the Project Link to Allow Unassigned issues.

Edit Field Configuration

(warning) Field configuration is currently a global operation in Enterprise Tester, all Enterprise Tester projects will have the AssignedTo field set as optional once this change is made.

To edit the field configuration and set the AssignedTo field as optional, you must:

  1. Navigate to the Admin tab
  2. Double Click on the Field Configuration folder
  3. Select Incident from the dropdown
  4. Untick the Required checkbox for the AssignedTo field

 

Creating the Connection

Create a Jira project link by navigating to the Resources tab and adding a Project Link, or by navigating to the Admin tab and Editing the External System, Link tab.  This process is documented here Synchronizing Incidents with JIRA or Synchronizing Requirements with Jira.

To allow Unassigned Issue synchronization you must:

  • Add or Edit a Project Link as per the above links.
  • Navigate to the External System Configuration tab.
  • Tick the checkbox called Allow Unassigned issues.
  • Complete the configuration as per the above links.

 

You will now be able to create Requirements or Incidents in Enterprise Tester that have no assignee, these will be synchronized to Jira as Unassigned.

External Systems Integration

Synchronizing Requirements with Jira

If you are using Jira for both requirements capture and defect management, Enterprise Tester is fully integrated to support the synchronization of both requirements and issues. Enterprise Tester supports full bi-directional synchronization of Requirements/User Stories with Jira. Key Features include:

  • Configurable import filtering by: Type, Status, Priorities, JQL fragments, Components, Affects Version(s), Fix Version(s);
  • Optional sub-task synchronization;
  • Configurable Synchronization Schedules — Adhoc (manual), Periodic (set time interval) and Daily;
  • Custom field support;
  • Jira ID on the requirement in ET;
  • Remote links to the Requirement in ET (and test script when linked) added on the Jira User Story; and
  • Jira workflow transition support from ET.

Once the Jira connection has been created, you can begin associating projects in the Jira with projects in Enterprise Tester.

Project links can be created and managed either from either External Systems in the Admin tab or from the Resources tab.

From the Admin tab, expand Extensions and double click on External Systems. From the External Systems summary grid, double click the External System you wish to create a link for.

Then navigate to the Links tab. Click on Add from the tool bar.

The Add External System Link screen will appear. Complete the name and select the Link Source, Requirements. This is the entity type you wish to synchronize.

Once you have selected the Source, additional fields to configure the ET project and the Jira project will appear.

Once you have completed the screen click on OK.

The External Links Details screen will appear. Now you will need to complete the Field Configuration and set up the synchronization schedule. See the Configure the Requirement Link section below.

Resources Tab

From the Resources tab in the navigation pane, click to expand “Project Links“. To view all configured links for your project, double click on your project.

  1. Click on the Resources tab in your tree navigator and click to expand ‘Project Link’.
  2. Right click on your project and select Add New Project Link, the Add External System Link screen will appear.
  3. Enter in the Name for the link, and select from the dropdowns: 

    • Source is the entity type you wish to synchronize. Select Requirements
    • The Enterprise Tester Project will be pre-selected
    • Destination is the configured external system to use for this link. Select your JIRA external system
    • Select the Jira Project to synchronize with.

Once the project requirement link is set up, you will be shown the screen below and will need to perform additional configuration.

From the Edit Synchronization Configuration screen, click on the ET Configuration tab. Select the ET requirements package you wish to synchronize with. Here you can also select the filter criteria when synchronizing from ET to JIRA. You can filter on Types, Statuses, and Priorities. Once you have completed your configuration, click Save.

Next, click on the External System Configuration. Select the entity type(s) (requirement, stories etc.) to synchronize with Enterprise Tester.

Here you can also select additional criteria including Statuses, Priorities, Components, JQL fragments, Affected and Fixed Version.

You can also select to synchronize sub-tasks related to the entities that meet your selection criteria. Note that the filter values only apply to the parent Requirement/User Story. All sub-tasks associate to these entities will also be synchronized when you select this option.

Additionally, you can choose to Allow Unassigned Issues (see Allow Unassigned issues to be synchronized with Jira).

Note that by default all entities will be synchronized if you do not apply a filter. If the Jira field values do not appear in the field drop down list, you may need to initiate a Refresh Lookups which will refresh the JIRA metadata.

Field Mapping

Next, click on the Mapping tab.

This screen displays two tabs for outlining and configuring the steps undertaken when synchronization is initiated.

• One tab for mapping fields from Enterprise Tester to the external system (Jira).
• One tab for mapping fields from the the external system (Jira) to Enterprise Tester

Task

Configurable

Description
Map Fields Yes Allows a set of mappings to be configured to transfer information between Enterprise Tester and the External System (Jira).
Map Attachments No Synchronizes the set of attachments between Enterprise Tester and External System (Jira). This will add new attachments that have not been synchronized previously, and remove previously synchronized attachments that have since been removed.
Create Trackback Comment No Adds a comment to the synchronized Jira requirement with the following text: Linked to Enterprise Tester requirement – e.g. Requirement: http://server/EnterpriseTester/#/requirement/edit/04e7f9e5-5784-4e94-a863-9ef600f0a935 (Name: ). If a comment already exists with the same value, then the comment is not added.

Next, set your field mappings in the direction of Enterprise Tester to External System — you will notice on the screen below that the Field Mapping is not currently configured. Please note that Enterprise Tester will prompt the administrator when a Refresh Lookups is either in progress or is required. This must be completed before configuring your field values. A Refresh Lookups will ensure that all the custom fields from your defect tracker and associated field values are up-to-date during field mapping.

You do not need to edit the mappings from the defect tracker to Enterprise Tester as they are already complete. However, you can edit them if required.

Click to highlight and select Map Fields and click on Configure from the toolbar. Please note that Enterprise Tester may need to Refresh Lookups before you can proceed with your field configuration.

From the Configure Fields mapping screen, several configurations are automatically created consisting of Copy Field type mappings and direct Map field type mappings.

The Copy Field type mappings are already configured and the value will be copied from Enterprise Tester to Jira on Synchronization:

Copy Field — Copy from ET: Name (field) to External System: Summary (field)
Copy Field — Copy from ET: Description to External System: Description (field)
Copy Field — Copy from ET: Created By (field) to External System: Reporter (field)
Copy Field — Copy from ET: Assigned To (field) to External System: Assignee (field)

The Map field type mappings require the field values to be mapped. You can see under the column Configured = False that the value for these fields has not yet been mapped:

Map Field — Map from ET: Type to External System: Type
Map Field — Map from ET: Priority to External System: Priority

  1. To complete the field mappings, click on the Type Map field and select Edit from the tool bar.
  2. Complete mapping Enterprise Tester field values to Jira field values.
  3. Click Save
  4. Complete mapping field values for Priority.

 

Notes on Field Type Support for Automap and Map Mapping Types

The following field types from Jira are not supported by the automap or map mapping types:

Field Type
Notes
Date Picker
Date Time Picker
Global Rank
Group Picker (multiple groups) This field is not supported natively in ET so you will need to use either the copy or set value mapping types
Group Picker (single group) This field is not supported natively in ET so you will need to use either the copy or set value mapping types
Hidden Job Switch
Job Checkbox
Labels
Text Field (multi-line)
Select List (cascading) ET does not have a cascading field to map this to. The only cascading field selected is copied from the defect tracker the “copy” mapping supports this field.
Text Field (read only)
Text Field (single line)
URL Field
User Picker (multiple users) As there may be many users, this isn’t suitable as a target for the “map” mapping type. The copy mapping could be used but the same username must exist in both ET and Jira.
User Picker (single user) As there may be many users, this isn’t suitable as a target for the “map” mapping type. The copy mapping could be used but the same username must exist in both ET and Jira.

 

Another point to note when configuring your field mapping configuration for Automap or Map type mappings is that you may need at least one value in your Jira picklist (configurable set of allowable values) for the field (drop down list, checkbox list etc.) for the field to be detected as a configurable field for these mapping types. After adding your value(s) to Jira you may need to perform a Refresh Lookups before the field will be detected.

Scheduling Requirement Synchronization

Now that your configuration and field mappings are complete you are ready to synchronize. The synchronization frequency can also be configured from the Schedules tab. There are 3 options that can be configured:

  1. Adhoc
  2. Periodic
  3. Daily

Note: For Periodic and Daily you can only synchronize Updated Since Last Synchronization.
If you select Synchronize All from the Scope drop down list when you select the Save button the following message will be displayed.

 

Type

Scope

Direction

Period

Time
Adhoc You can choose to only Update entities since the last synchronization or Synchronize All Four options:
• To External System (From ET)
• From External System (To ET)
• Bi-Directional (External System changes will synch first)
• Bi-Directional (ET changes will synch first)		 N/A N/A
Periodic You can only Update entities since the last synchronization Four options:
• To External System (From ET)
• From External System (To ET)
• Bi-Directional (External System changes will synch first)
• Bi-Directional (ET changes will synch first)		 Specify the synchronization frequency in minutes N/A
Daily You can only Update entities since the last synchronization Four options:
• To External System (From ET)
• From External System (To ET)
• Bi-Directional (External System changes will synch first)
• Bi-Directional (ET changes will synch first)		 N/A Specify the time using the (24hr clock) when the synchronization will occur daily

Once you have configured your synchronization frequency, a summary of the configured synchronization schedules is available. You can see the time of the Last Run, the Next Run (if applicable), whether the schedule is enabled or not and the current Synchronization Status.

You can use the toolbar to add a newly scheduled synchronization, delete an existing configuration, enable or disable an existing schedule, configure an existing schedule or manually initiate a synchronization.

Synchronization History

You can view the Synchronization history from both the Synchronization Configuration screen and the individual synchronized entities. From the configuration screen, you can view all synchronization events, select to only view errors, export the synchronization events to a CSV file or clear the history.

Deleting requirement project links will stop the synchronization between Enterprise Tester and your external system. When deleting the link you will have the option to delete the link and remove all external link references or to retain these references. These include the trackback comments and the defect issue link placed in Enterprise Tester. Note that if you chose to delete the references, this will only affect Enterprise Tester. References to Enterprise Tester in your external system cannot be removed, but all references in Enterprise Tester to your external system will be removed.

Limitations

  • When synchronizing from ET to Jira, the requirement to requirement relationships in ET are synchronized to Jira.
  • When synchronizing from Jira to ET, links between issues in Jira are not synchronized to relationships in ET
  • Requirement Synchronization to Jira does not currently support mapping to/from cascading select fields. When synchronizing from ET to Jira, if you see an error message similar to this with the error “is an invalid parent option” this suggests you have tried mapping to a cascading select field: 
    System.ServiceModel.FaultException: com.atlassian.JIRA.rpc.exception.RemoteValidationException: Fields not valid for issue: Errors: {customfield_10130=The option '1' is an invalid parent option} Error Messages: Remove the mapping to allow synchronization to work once again.
  • Auto-map from ET to Jira is not currently implemented (field values from ET are not added to Jira automatically as they are in the Jira to ET direction when using the auto-map feature).