JAM Plugin - Jira

11909 916 AMGo2Group JaM Plugin - Installation Guide for Latest Version - JaM Plugin - Go2Group Customer Support Wiki

Page 1 of 56httpgo2groupcomdisplayPluginJaMGo2Group+JaM+Plugin+-+Installation+Guide+for+Latest+Version

Added by W Anderson last edited by W Anderson on Nov 09 2009

Go2Group JaM Plugin - Installation Guide for Latest Version

01 Download

02 Recent Updates

03 Documentation

04 Literature

05 JaM Support

06 JaM FAQ


The Go2Group JaM Plugin - Installation Guide provides users with a full description for installing and configuring the Go2Group JaM Plugin This guide is to beused with the latest version of the Go2Group JaM Plugin

This document applies to versions 57 amp 58

Before diving into the full installation guide below we highly suggest starting with the Quick Install guide The Quick Install guide providessteps to install and configure the Go2Group JaM Plugin in a default environment with the goal to ensure communication between JIRA andQC is established

Once the Quick Install guide has been completed and communication has been established and confirmed using the guide below willprovide steps to further customize the integration to meet your environment needs

Grab the PDF Here



Go2Group JaM Plugin OverviewGo2Group JaM Plugin Use Cases

Go2Group JaM Plugin RequirementsWhats NeededWhere to Get Help

Go2Group JaM Plugin Whats New in This VersionGo2Group JaM Plugin Installation

Installation OverviewInstallation AssumptionsInstallation StepsThe Quality Center Soap ServiceThe Quality Center Kit Plugin for JIRA

WebLogic WebSphere Linux JIRA WARMicrosoft Windows Environments

Quality Center Sync ServiceQuality Center Sync Listener

Quality Center DefectsGo2Group JaM Plugin Configuration

Attachment ReplicationComment Replication

Replicating comments into different fieldsReplicating comments in the comment field directly

Replication with HTML formatDefine multiple configurationsOne QC project to many JIRA projectsDisable replicationWorkflow violations interceptionSupport QC Filter

Go2Group JaM Plugin UsageForcing Replication from Quality Center to JIRAForcing Replication from JIRA to Quality Center

Go2Group JaM Plugin Tips and TroubleshootingGeneral SuggestionsUpdates and UpgradesFrequently Asked Questions

Go2Group JaM Plugin Additional InformationTechnical SupportSales SupportLearn More

Go2Group JaM Plugin Appendix A - Repository InstallationGo2Group JaM Plugin Appendix B - Defect Replication StrategyGo2Group JaM Plugin Appendix C - Forcing Replication from JIRA to Quality CenterGo2Group JaM Plugin Appendix D - Field TypesGo2Group JaM Plugin Appendix E - How to Disable the JaM Plugin



Go2Group JaM Plugin OverviewThe Go2Group JIRA add-on for HP Quality Center (JaM) Plugin allows developers in JIRA to display a list of available Quality Center (QC) test cases in aJIRA window When viewing a JIRA issue each associated test case andor requirement will be displayed in the JIRA issue tab panel allowing developers toquickly review associated test cases defects and requirements

From the QC side the Go2Group JaM Plugin runs automatically - there is no direct user interaction needed The Go2Group JaM Plugin tells QC which JIRAissues are associated with a test case defect and requirement and displays the related information within QC



The bi-directional nature of the Go2Group JaM Plugin provides several valuable points

Developers no longer need to periodically export the issue status from JIRA to update managementQuickly finds test cases andor requirements related to specific JIRA issuesQuickly finds test cases andor requirements related to specific JIRA issuesProvides a free flow of information between developers and testers including attachment synchronization between the two systems and teams



Go2Group JaM Plugin Use CasesActors - All members of the Test and Development Teams including

Test engineers using QCDevelopers using JIRACodepeer review participants

Products Involved

Atlassian JIRAHP Quality Center

Questions Being Answered

Which developer is working on which defectWhat state is a specific defect inWhat comments are availableWhat attachments were available for validationWho reviewed the changes

Use Case Example

Requirement logged in QCDeveloper is assigned the issue in JIRADeveloper performs work on issueDeveloper marks the issue as resolved and transitions the issue to QCTester resumes work on defect testing

For a more thorough Use Case Example please visit Go2Group JaM Plugin Use Case Example

Go2Group JaM Plugin RequirementsWhats Needed

Atlassian JIRA Enterprise v311 or laterHP Quality Center v90 or laterJDK 15 or later

In addition to the technical requirements above you will need administrator-level permissions for Atlassian JIRA HP Quality Center and the Application Server

The Go2Group JaM Plugin supports HP QC v100



Where to Get HelpGo2Group provides support for its entire line of products by telephone email and a product-specific customer support ticket system

By telephone 877 442 4669

By email supportGo2Groupcom

By ticket jiraGo2Groupcom

A customer account is required to access the support site above Please contact Go2Group for your login credentials

For support with JIRA please contact your Atlassian representative

For support with Quality Center please contact your HP representative

Go2Group JaM Plugin Whats New in This VersionGo2Group is excited to announce the availability of version 57 of the Go2Group JaM Plugin Below we have highlighted a few enhancements and updatesfound in this latest version For a full list of updates please visit the Go2Group JaM Plugin Recent Updates page

Forcing replication from Quality Center to JIRA by choosing date range

You can use the JaM Plugin to replicate defects updated or created within specified time period Click the Replicate QC Defects link in the JAM configuration



Choose Replicate All or duration replication streagegy Then click Run Now

Support user type custom field replication

The Go2Group JaM Plugin now supports user type replication Before version 57 only reporter and assignee fields could be replicated between the twosystems In version 57 user type custom fields can now be replicated between JIRA and QC



mercurypropprties can be saved into JIRAs DB

The Go2Group JaM Plugin now supports the ability to move the mercuryproperties configuration file into JIRAs database for backup configurations with JIRA

Please backup all the configurations (mercuryproperties files) first After migration all properties will be deleted

Step 1 Click the Move Properties file into JIRAs DB link



Step 2 Click Transform to move properties into JIRAs DB

Configure the Last Replication TimeThe Go2Group JaM Plugin now supports the adjustment of the last replication time from within a GUI configuration screen Previously the lasttimefile file wasedited to adjust the last synchronization time

Step 1 Click Configure Last Replication Time

Step 2 Configure the time



Go2Group JaM Plugin Installation

Installation OverviewThe installation and configuration of the Go2Group JaM Plugin is straightforward - install the Go2Group JaM Plugin components configure the Go2Group JaMPlugin and test the configuration The following section provides details for the installation process

It is beneficial to note at this time that the majority of setup delays occur when mapping fields between Quality Center and JIRA The configuration sectionprovides a robust set of steps to assist with the mapping of required standard and custom fields between JIRA and Quality Center

Go2Group highly encourages a review of fields that users want mapped BEFORE configuring the Go2Group JaM Plugin This review should include

Required Fields - Those fields in JIRA and QC that are requiredStandard Fields - Those fields in JIRA and QC that need to be mapped (ie status priority etc)Custom Fields - Those fields added in JIRA and QC to serve the customers custom environment

At a very basic level there are two servers involved - the Quality Center server and the JIRA server - and a soap service that provides communicationbetween the two servers The Go2Group JaM Plugin is configured within the JIRA server If you are using QC on Linux then you need to run the QualityCenter soap service on a Windows machine

The packaged installer can be run using the installer on Windows or installsh on Linux The installer will perform some of the installation steps for JIRA theweb service or both

The instructions below indicate which parts of the installation will be done by the installer and which have to be performed manually



Installation AssumptionsPlease ensure the following steps have been completed prior to beginning the installation process

A local copy of the Go2Group JaM Connector installation file has been downloaded from the Go2Group website (wwwGo2Groupcom)A license key has been requested received from Go2GroupThe user installing the Go2Group JaM Plugin has the appropriate privileges to the JIRA and QC servers along with the connected database(s)The user installing the Go2Group JaM Plugin has coordinated with the appropriate administrators and teams to obtain support and recycle the serversGo2Group recommends evaluating the Go2Group JaM Plugin in a test environment

Installation StepsThe installation process consists of four sections

The Quality Center Soap Service (aka Go2Group Mercury Soap Service)The Quality Center Kit Plugin for JIRAThe Quality Center Sync ServiceThe Quality Center Sync Listener

Each of these sections is explained in detail below

The Quality Center Soap ServiceThe Quality Center Soap Service is a Java web service component that is installed on a Windows machine While the Go2Group JaM Plugin supports QualityCenterJIRA running in a Linux environment the Go2Group JaM Plugin utilizes a web service to communicate with QC via HPs API and this service must beinstalled and run on a Windows machine - Windows XP or Windows 2003 Server are acceptable versions of Windows

At this time HPQC only supports a COMWindows API which must be available on a Windows machine

If Quality Center andor JIRA is installed on Linux in your environment a separate Windows machine can be used to install the Quality Center SOAP service

Requirements

The Quality Center API libraries must be available on the Quality Center server these are automatically installed by logging in to Quality Center from aweb browserJAVA_HOME is available and configured properly in the system variable and the version of JDK is 15 or above You can download JDK from SunsJDK and configure JAVA_HOME in system environmentPorts 2098 2099 4560 and 5444 should be available on the installed machineIf Quality Center is in a Linux environment the Quality Center Soap Service must be installed on a Windows machine which can then log in to QualityCenter from a web browserIf a Network Attached Storage device is configured as the Quality Center data repository AND the Quality Center Soap Service is being installed on thesame machine as Quality Center please review Appendix A



Begin the Quality Center Soap Service installation process by running the Mercury_SOAP_Serviceexe file found in the downloaded Go2Group JaM Pluginpackage The Welcome screen appears

Click the Next button to continue

Review and agree to the Go2Group Software EULA




Verify JDK 15 or higher is installed and ports 2098 2099 and 4560 are available




Select the destination where the Quality Center Soap Service should be installed




Specify the web service port for the Quality Center Soap Service Please note that if you install soap service on QCs box dont specifiy QCs port number



Click the Next button to complete this part of the installation

Start the Go2Group Quality Center (Mercury) Soap Service from the Windows Services panel



Please note - If SSL is used for Quality Center the Go2Group Quality Center Soap Service can be started by either logging in as an administrator or by usingthe following command line

ltSOAP_SERVICEgtbinrunbat

Once the Go2Group Quality Center Soap Service has started verify the web service is available by accessing the following URL in an Internet Explorer webbrowser

httpserverportMercuryInterfaceMercuryInterfacewsdl



For example

httplocalhost8080MercuryInterfaceMercuryInterfacewsdl

If the web service is available a screen resembling the following image should appear

The Quality Center Kit Plugin for JIRAThis section describes how to install the Quality Center Kit Plugin for JIRA The following environments are discussed below



WebLogic WebSphere Linux JIRA WAR environmentsMicrosoft Windows environments

WebLogic WebSphere Linux JIRA WARUntar the following file found in the latest Go2Group JaM Plugin package Mercury_Kit_JIRA_Plug-in_unixtargz Once complete find the followingmercury_kit jar file

libmercury_kit-jar

Copy the libmercury_kit-jar directory into the WEB-INFlib directory on the JIRA machine

To verify whether the Go2Group JaM Plugin successfully loaded check the JIRA Plugin Repository as shown in the image below



Before continuing ensure the Quality Center Soap Service is installed and configured (see previous section)

Microsoft Windows EnvironmentsInstall the plugin JAR file by running the Mercury_Kit_JIRA_Plug-in_windowsexe file found in the Go2Group JaM Plugin package Next specify thelocation of JIRA



click Next then Finish button to complete this sectionOnce the Quality Center Kit Plugin for JIRA has been installed navigate to the Administration section of JIRA and select the JaM Configuration link under theSystem settings



Next click the Initialize JaM link

After clicking the Initialize JaM link you are presented with the JaM Configuration screen which will build specific custom fields a sync service and a syncservice

Please select the module(s) that is (are) appropriate for your environment and needs then click the Initialize JaM button



Please note - It is important to review each of the custom fields following the initialization of the Go2Group JaM Plugin The following section explains whichcustom objects are created during the initialization of the Go2Group JaM Plugin

Defect Module

CustomFieldName

CustomObjectType

Description

QcBugId Text Field Field - This field should not be visible on any screen it merely holds the ID of the Quality Center defect that corresponds to theissue in JIRA Make sure the QcBugId is applied to the project you want to replicate



Quality Center Sync ServiceCustom Field Name Custom

ObjectType

Description

Quality Center(Mercury) SyncService

Service A 1-minute delay is set as the default The default setting is ideal for using the Go2Group JaM Plugin in testenvironments Once released to production a 5-minute delay may be more acceptable



Quality Center Sync ListenerCustom Field Name Custom Object Type Description

Quality Center Sync Listener Listener Noted as QC Listener below



Test Case Module

Custom Field Name Custom Object Type Description

TestCases MercuryField Placed on the default screen Ensure the TestCases field is applied to project you want to replicate

Requirements Module


Requirements Requirement Field Placed on the default screen Ensure the Requirements field is applied to each project you want to replicate

Quality Center DefectsIf defects need to be replicated between JIRA and Quality Center a custom field in Quality Center will need to be created that will hold a corresponding JIRAissue key The field type should be set to String The name is not important since Quality Center uses an internal identifier for custom fields but a descriptivename like JIRA ID is appropriate This field name (eg BG_USER_06) should be the same as bugfield in mercuryproperties

This is a required field

To review the process of creating a custom field in Quality Center please click here



Go2Group JaM Plugin ConfigurationThe Go2Group JaM Plugin provides a GUI configuration panel to configure different features and settings for your specific environment The GUI configurationpanel is accessible by clicking the JaM Configuration link found in the administration section of JIRA as shown below

Administration gtgt System gtgt JaM Configuration



Please note When you save the settings in the final step(step 4) of the configuration it will update the Go2Group JaM Plugin immediately Restarting JIRA isnot needed

The JaM Configuration welcome screen provides a few pieces of key information as shown in the image below



File Name Name of the properties file holding the configuration of the JaM Plugin

OperationsEdit Make changes to the configuration of the Go2Group JaM PluginCopy Make a copy of the current configuration of the Go2Group JaM Plugin (backup multiple QC projects)Download Download a copy of the current configuration of the Go2Group JaM Plugin (provide to Go2Group for support)Replicate QC Defects Manually sync defects from Quality Center (used mainly during evaluation and testing) Please note Tomanually force a replication from JIRA review Appendix C

Status Enabled or disabled

Organization Organization using an evaluation or production copy of the Go2Group JaM Plugin

LicenseType

Type of license initialized Trial or Production

LicenseExpires

For evaluation license the expiration date of the evaluation license For production licenses the support and maintenance expiration date

Note Additional notes for this implementation of the Go2Group JaM Plugin

Clicking the Edit link in the JaM Configuration allows the configuration to be changed After the Edit link has been clicked the following screen appears



Mercury SOAP ServiceURL

This field defines the address of the SOAP service as it is deployed in an application server on QC

Quality Center URL This field defines the QC URL

Quality Center User This field defines password used to authenticate with QC

Quality CenterPassword

This field defines the Quality Center user name used to authenticate with QC

JaM License Evaluation or Production license provided by Go2Group Please note - this license string should be three (3) lines The abovelicense is inactive


The next screen displays the project mapping between Quality Center and JIRA In the example below the project named DEMO in JIRA is being replicated tothe project named QualityCenter_Demo in Quality Center Since this project needs bi-directional synching the project named QualityCenter_Demo in Qualitycenter is replicated to the project named DEMO in JIRA To map an additional project for Issues Test Cases or Requirements click the Add Project Mappinglink and populate the required fields




The next screen assist in configuring the common properties of the Go2Group JaM Plugin While not all properties will be completed in every environment it isimportant to review each Key and Value to ensure the Go2Group JaM Plugin is customized for your specific environment






The final configuration screen appears It is very important this configuration section is reviewed after completion Most configuration questions are solved byreviewing and adjusting these settings For more information on the available field types please see Appendix D

Please note - All REQUIRED fields in both JIRA and Quality Center MUST be mapped Custom fields are mapped in this section as well To add an additionalfield mapping simply click the Add Field Mapping link and populate the required fields



Click the Submit button to return to the JaM Configuration welcome screen

Attachment ReplicationIf you want to have Attachment Replication you have to specify the Attachment replication in the Field Mapping Configuration



Comment Replication

Please note (Updated) If the user who made the comment in QC doesnt exist in JIRA then JIRA will log an error and fail to send theemail The user in Quality Center who makes the comment does not need to be a registered JIRA user When the comment notification istriggered comments will appear to come from the sync user and all the information will be included

Comments are handled very differently in JIRA and Quality Center In JIRA comments are stored as a log of individual entries In Quality Center commentsare stored in one field as one block of text with HTML markup used to format the fields appearance And in Quality Center comments are only recorded in dayformat without hours and minutes For this reason comments cannot be synchronized like regular fields We provide two different ways for you to replicatecomments

Replicating comments into different fieldsComments can be displayed in both systems The Quality Center comment field BG_DEV_COMMENTS can be synchronized like a normal text field with anysuitable JIRA field such as Environment or a text custom field With this approach comments from Quality Center can be displayed in JIRA (Updates made tothis comment field in JIRA will be replicated to Quality Center)



JIRA comments can be sent to any suitable Quality Center field All comments in a JIRA issue will be aggregated into one formatted block of text when storedin Quality Center In other words all JIRA comments for an issue will be stored in one field in Quality Center Updates made to that field in Quality Center willbe ignored during replication and overwritten if more JIRA comments are sent over later

Replicating comments in the comment field directlyComments between JIRAs comment field and QCs comments are directly synced while preserving HTML formatting in Quality CenterPlease review the following restrictions

First in order to parse the correct comments in Quality Center you need to keep the default comment format in Quality Center such as the horizontallineusername and date format If you change the format of the comment then that comment wont be replicated to JIRA Second since we need to parse the comments date If you have different time format other than yyyyMMdd(20081116) orMMddyyyy(11162008) you need to configure commentDateFormat in the mercuryproperties

Third deleting a comment in JIRA wont trigger the comment to be deleted in Quality Center

Fourth if you update the comment that was replicated from JIRA to Quality Center it wont sync back to JIRA and vice versa

Item Precaution Note

Create commentin JIRA

Comments will be replicated into QC

Update commentin JIRA

Comments will be replicated in QC We dont support comment updates being replicated to QC

Delete commentsin JIRA

We dont support comment deletes If you delete a comment in JIRA please delete the comment inQuality Center manually

Create commentin QC

Comments will be replicated to JIRA

Update commentin QC

The previous comment in JIRA will be deleted and a new commentwill be created in JIRA

We dont support comment updates being replicated to JIRA

Remove commentin QC

Comment will be deleted in JIRA

You also need to configure comment type for comment replication



Below are a few screenshots of the comment replication feature



Replication with HTML formatField replication can occur with HTML formatting Please note only description and comment(replicating comments into different fields) support html formatreplication In order to take advantage of this feature the Wiki Render Macros Plugin module must be enabled To enable this module follow the instructionsbelow

1Enable html support in Wiki Render Macros Plugin (see image below)

2 You need to use Wiki Style Render for the field (like QC Comment custom Description field) You can configure this by entering Field Configurations |Default Field Configuration | QC Comment in the Administration console (see image below)




Define multiple configurationsYou are allowed to define multiple settings for replication You only need to define multiple configurations You can use the copy operation in our configurationPlease note that the file name of the different configurations must start mercury and end with properties A few examples follow

mercurypropertiesmercury2properties

One QC project to many JIRA projectsWe support one QC project maps to many jira projects You only need to follow the stepsStep 1 Create a custom field in Mercury with a name such as JIRA Project Name and field type Lookup List in Defect module Then create a new list whichcontains all the jira project names





Step 2 Configure jiraprojectfield property in the configuration

Disable replicationYou are allowed to stop replication by disabling specific properties in configuration All the replication policies defined in this properties file will be disabled Thisis useful when you are still configuring the replication and do some test But you cant disable the main one which is mercuryproperties



Workflow violations interceptionYou are allowed to update defect to any status in Mercury but you could easily break the workflow in JIRA We support not to execute workflow if the data ofissue is not validated for workflow but the data still being replicated to issue except status You can enable stopStatusChangeIfWorkflowViolatione propertythrough configuration

You can also specify a custom field for holding the message when workflow violations happen by adding a free text custom field for logCustomField property

Support QC FilterYou can define QC filters to support replication from QC to JIRA This value holds the filters of QC and provides the flexibility of controlling replicationex if youwant to restrict only defects with value Mercury Tours Web Site in project field(BG_PROJECT) join the replication You can specify BG_PROJECTMercuryTours Web SiteWe also support multiple filters by separator | We suggest you test filter in QC before configure



Go2Group JaM Plugin UsageUsing the Go2Group JaM Plugin is easy When editing an issue JIRA will display a list of available Quality Center Test Cases in the custom field calledTestCases Select one or more Test Cases to associate with the JIRA Issue

JIRA will display a list of available Quality Center Requirements in the custom field called Requirements Select one or more Requirements to associate withthe JIRA Issue



the JIRA Issue

When viewing an issue JIRA will display information about each associated Test Case and Requirement in an issue tab panel as shown below



At the same time the link between Test Plan and Defect will be updated automatically in Quality Center

The link between Requirement and Defect in Quality Center is also updated



When browsing a project JIRA will display information about all of the Test Cases linked to any issue in the project using a project tab panel You can alsofilter issues by configuring a JIRA filter



When browsing a project JIRA will display information about all of the Requirements linked to any issue in the project using a project tab panel You can alsofilter issues by configuring a JIRA filter



You can also search for issues that contain certain Test Cases or Requirements as shown in the image below

Forcing Replication from Quality Center to JIRAYou can use the JaM Plugin to replicate defects updated or created within a specified time period

Click the Replicate QC Defects link in the JAM configuration



Choose Replicate All or specify a duration

Forcing Replication from JIRA to Quality CenterInstead of using the Replicate Now action you can replicate groups of issues through the use of filters All the matching JIRA issues will be replicated intoQuality Center immediately This function can also be used to migrate all JIRA issues into QC The feature is available for users who have ProjectAdministration permissions



Go2Group JaM Plugin Tips and TroubleshootingGeneral SuggestionsGo2Group provides technical support for its entire line of products If you run into any issues when installing or configuring the Go2Group JaM Plugin pleasecontact us

Updates and UpgradesGo2Group provides regular updates to its products These updates include performance enhancements and minor bug fixes

To review previous current and upcoming updates and upgrades please visit the Go2Group support site

Frequently Asked QuestionsGo2Group provides an updated list of frequently asked questions

Go2Group JaM Plugin Additional InformationTechnical SupportGo2Group provides technical support for its entire line of products including the Go2Group JaM Plugin

Go2Group technical support is available by telephone email and a Go2Group JaM Plugin specific customer support ticket system

By telephone +1 877 442 4669By email supportGo2GroupcomBy ticket jirago2groupcom



A customer login is required to access the support site above The login process is self-administered

To help resolve your issue quickly please provide the log files from the Go2Group JaM Plugin as follows

download all the configurations(mercuryproperties) from the JaM Configurationatlassian-jiralog (ltJIRA_HOMEgtatlassian-jiraWEB-INFclassesmercuryproperties)

Please change log level by adding log4jcategorycomgo2group=DEBUG console filelog and log4jadditivitycomgo2group = false inlog4jproperties Restart JIRA and run some test cases You can find log4jproperties in ltJIRA_HOMEgtatlassian-jiraWEB-INFclasses

qc2009-MM-ddlog (ltSOAP_SERVICE_HOMEgtlogsqclog)

Sales SupportGo2Group provides sales support for its entire line of products including the Go2Group JaM Plugin

Go2Group sales support is available by telephone and email

By telephone +1 877 442 4669By email salesGo2Groupcom

A customer login is required to access the support site above Feel free to add credentials at your convenience

Learn MoreFor more information on Go2Group its products and its services please visit our website at wwwGo2Groupcom

For more information on JIRA please visit the Atlassian website at wwwAtlassiancom

For more information on Quality Center please visit the HP website at wwwHPcom

Go2Group JaM Plugin Appendix A - Repository InstallationThis section is required ONLY when you install the Go2Group Quality Center (Mercury) Soap Service on the same machine Quality Center is installed onAND a Network Attached Storage device is configured as the repository

If you installed the soap service on another Windows machine you can ignore this section

For attachments the soap service needs access to Quality Centers repository If your Quality Center repository is on the local hard drive this permissioncheck can be skipped

However if the Quality Center repository is located on a Network Attached Storage device or other network share system the same account that is used tostart Quality Center must be used to startup the soap service

The repository information is available through Quality Centers Site Administration In the example below the repository is on a Network Attached Storagedevice



The Go2Group Quality Center (Mercury) Soap Service needs to access the Network Attached Storage device in the same manner that Quality Center doeswhen a Network Attached Storage device is configured as a base repository To access the Network Attached Storage device the soap service must bestarted with the same account as starting Quality Center

The image below displays the optional Log On tab for a specific Windows service



Go2Group JaM Plugin Appendix B - Defect Replication StrategyWhen performing defect replication a strategy is required to avoid double replications That is unless precautions are taken an issue replicated from QualityCenter to JIRA may trigger a reverse replication from JIRA to Quality Center

The following table lists the precautions taken to avoid this problem in the four replication scenarios

Scenario Precaution Notes

NewJIRAissuecreated

Will not be replicated to Quality Center if the project isnot marked for replication if the issue already has aQuality Center ID stored with it or if the issues creator isthe special synchronization JIRA account

JIRA issue ID is stored with the replicated Quality Center issue and the JIRA issueis updated with the ID of the corresponding Quality Center defect

JIRAissueupdated

Will not be replicated to Quality Center if the project isnot marked for replication or if the updating user is thespecial synchronization JIRA account

JIRAissue

Deleting a defect in JIRA will cause the corresponding defect in Quality Center tobe deleted



issuedeleted

be deleted

NewQualityCenterissuecreated

Will not be replicated to JIRA if the project is not markedfor replication or if the issue already has a JIRA IDstored with it

Replicated JIRA issue ID is stored with the original Quality Center issue and theJIRA issue is updated with the ID of the original Quality Center defect Thesynchronization user account is used to create the issue in JIRA

QualityCenterissueupdated

Will always be replicated in JIRA but the JIRA listenerwill ignore that update since it comes from thesynchronization user account

The synchronization user account is used to update the issue in JIRA

QualityCenterissuedeleted

Deleting a defect directly in Quality Center will not affect the corresponding JIRAdefect currently we have no way to monitor defects deleted manually in QualityCenter Generally deleting defects is a rare event We recommend that defects bedeleted if required in JIRA rather than Quality Center

Go2Group JaM Plugin Appendix C - Forcing Replication from JIRA to QualityCenterIn order to force JIRA issues to immediately replicate to Quality Center use the Replicate Now issue operation This operation is available for issues that areeligible for replication as specified in mercuryproperties Additionally a user must have permission to edit the issue or the operation will not be available

The operation will immediately attempt to replicate the JIRA issue to Quality Center If the issue has never been successfully replicated it will be treated as anew defect creating a new defect in Quality Center If it has been replicated in the past it will be synchronized with its corresponding Quality Center defect

When the operation is complete the issue page will reload You may have no indication that the replication occurred but you should see the updates inQuality Center



Go2Group JaM Plugin Appendix D - Field TypesThere are several field types you can specify during the field mapping configuration of the Go2Group JaM Plugin The table below provides the field types andtheir descriptions

Field Type Description

String

Number

Date Will be translated using a standard date format

Version Used for single version picker version picker custom fields in JIRA

Multi Used for multi-select multi-checkboxes custom fields in JIRA

Cascade Used for cascading-select custom fields in JIRA and replicate to a list field in Quality Center

Comment Used to replicate comments

HTML Used to keep html format from Quality Center You can use this type for Description and Comment

User If you use user type custom field in JIRA you need to use this type for replication



Go2Group JaM Plugin Appendix E - How to Disable the JaM PluginIf you need to disable the Go2Group JaM Plugin for a short duration please disable the replication You can find information on disabling replication in theDisable Replication section within Go2Group JaM Plugin Configuration section

To remove the Go2Group JaM Plugin completely please review the following steps

Disable the Mercury-Kit Module from JIRA PluginsRemove the MercuryListenerRemove the MercuryService

If theres a particular reason youd like to share with us for removing the Go2Group JaM Plugin wed enjoy hearing from you

Go2Group JaM Plugin Home Space


Printed by Atlassian Confluence 301 the Enterprise Wiki



Go2Group JaM Plugin OverviewGo2Group JaM Plugin Use Cases

Go2Group JaM Plugin RequirementsWhats NeededWhere to Get Help

Go2Group JaM Plugin Whats New in This VersionGo2Group JaM Plugin Installation

Installation OverviewInstallation AssumptionsInstallation StepsThe Quality Center Soap ServiceThe Quality Center Kit Plugin for JIRA

WebLogic WebSphere Linux JIRA WARMicrosoft Windows Environments

Quality Center Sync ServiceQuality Center Sync Listener

Quality Center DefectsGo2Group JaM Plugin Configuration

Attachment ReplicationComment Replication

Replicating comments into different fieldsReplicating comments in the comment field directly

Replication with HTML formatDefine multiple configurationsOne QC project to many JIRA projectsDisable replicationWorkflow violations interceptionSupport QC Filter

Go2Group JaM Plugin UsageForcing Replication from Quality Center to JIRAForcing Replication from JIRA to Quality Center

Go2Group JaM Plugin Tips and TroubleshootingGeneral SuggestionsUpdates and UpgradesFrequently Asked Questions

Go2Group JaM Plugin Additional InformationTechnical SupportSales SupportLearn More

Go2Group JaM Plugin Appendix A - Repository InstallationGo2Group JaM Plugin Appendix B - Defect Replication StrategyGo2Group JaM Plugin Appendix C - Forcing Replication from JIRA to Quality CenterGo2Group JaM Plugin Appendix D - Field TypesGo2Group JaM Plugin Appendix E - How to Disable the JaM Plugin













Products Involved




Use Case Example
























































Requirements































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number





























Products Involved




Use Case Example
























































Requirements































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number

























Products Involved




Use Case Example
























































Requirements































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number





















Products Involved




Use Case Example
























































Requirements































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number


































































Requirements































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number






















































Requirements































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number

















































Requirements































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number











































Requirements































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number





































Requirements































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number



























Requirements































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number














































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number









































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number





































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number

































For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number





























For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number

























For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number



















For example








libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number





















libmercury_kit-jar


















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number
































Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number




























Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number

























Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number




















Defect Module

CustomFieldName

CustomObjectType

Description





ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number




















ObjectType

Description









Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number























Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number



















Test Case Module



Requirements Module




















LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number































LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number



























LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number























LicenseType


LicenseExpires
































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number













































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number


































Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number






























Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number




























Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number























Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number



















Comment Replication


















Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number































Create commentin QC


Update commentin QC



Remove commentin QC


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number
















































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number













































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number








































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number


































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number
































the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number




























the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number























the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number



















the JIRA Issue


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number









































































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number





































































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number


































































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number































































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number


























































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number






















































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number













































NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number


























NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number






















NewJIRAissuecreated



JIRAissueupdated


JIRAissue




issuedeleted

be deleted
















String

Number



















issuedeleted

be deleted
















String

Number





















String

Number


























Documents

JAM Plugin - Jira