Date: Thu, 28 Mar 2024 15:13:43 +0000 (UTC) Message-ID: <868941871.8747.1711638823385@catch-kbase-p> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8746_97627499.1711638823384" ------=_Part_8746_97627499.1711638823384 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Introduction
If you are migrating a JIRA server to a new location, and as a resu= lt, the URL of the server changes, then you will need to manually repair so= me data in the database to make Enterprise Tester aware of these changes.= p>
For the purpose of this KB article, we will assume that from and to URL'= s for JIRA are:
Before making any changes we suggest that you:
Incidents within the ET database are stored across a number of tables. T= he table that needs updating when changing the JIRA URL is called "Inc= identDetails", and in particular, a column called "TicketKey".
You will need the assistance of your DBA to run these queries against yo= ur Enterprise Database.
Database Type |
|
Sql Server |
UPDATE IncidentDetails |
Oracle |
UPDATE INCIDENTDETAILS |
MySql |
UPDATE IncidentDetails |
PostgreSql |
UPDATE IncidentDetails |
For requirements synchronized to JIRA, the JIRA information is stor= ed in a table called "ExternalSystemReferences". As with incidents above, i= t is necessary to search and replace the values of the old server name with= the new server name but instead using the column "ExternalUrl".
Database Type |
|
Sql Server |
UPDATE ExternalSystemReferences |
Oracle |
UPDATE EXTERNALSYSTEMREFERENCES |
MySql |
UPDATE ExternalSystemReferences |
PostgreSql |
UPDATE ExternalSystemReferences |
In version 4.5 and above of Enterprise Tester, additional columns store = URLs to other assets associated with JIRA for requirement sync:
ExternalIconUrl |
UPDATE ExternalSystemReferences |
ExternalStatusIconUrl
|
UPDATE ExternalSystemReferences |
ExternalStatusIconLink
|
UPDATE ExternalSystemReferences |
ExternalIconUrl |
UPDATE EXTERNALSYSTEMREFERENCES |
ExternalStatusIconUrl
|
UPDATE EXTERNALSYSTEMREFERENCES |
ExternalStatusIconLink
|
UPDATE EXTERNALSYSTEMREFERENCES |
ExternalIconUrl |
UPDATE ExternalSystemReferences |
ExternalStatusIconUrl
|
UPDATE ExternalSystemReferences |
ExternalStatusIconLink
|
UPDATE ExternalSystemReferences |
ExternalIconUrl |
UPDATE ExternalSystemReferences |
ExternalStatusIconUrl
|
UPDATE ExternalSystemReferences |
ExternalStatusIconLink
|
UPDATE ExternalSystemReferences |
Also from v4.5 and above of Enterprise Tester, the log messages stored f= or synchronization may contain hyperlinks. These can be replaced as follows= :
Database Type |
|
Sql Server |
UPDATE ExternalSystemEvents |
Oracle |
UPDATE EXTERNALSYSTEMEVENTS |
MySql |
UPDATE ExternalSystemEvents |
PostgreSql |
UPDATE ExternalSystemEvents |
Once you have searched and replaced all the data, execute some SELECT st= atements across the tables you have updated and confirm the URLs have been = replaced correctly. We suggest running the following statement:
SELECT = TicketUrl FROM IncidentDetails WHERE TicketUrl IS NOT NULL
Next, try some of the TicketUrl values generated within your browser to = confirm that you get back the expected issue (to confirm the URL is not mal= formed).
Once you are happy with the data updates, you can follow these ste= ps to bring everything back online:
Try the following tests: