Work Item Description Links
Hello,
I have completed a migration from RTC/Jazz V2.0 on a test machine that is not the machine that the original repository is stored. Upon completing the migration, some users noticed that some of the links embedded withing existing work item descriptions were still pointing to the original (actual) server instead of the newly migrated test server and seem to hard coded that way. Is there a way to alleviate this issue in order to keep this from happening during the actual migration? Or is this simply something that will "fix itself" when the migration is performed on the actual server? Thank you for your help.
-Mike
I have completed a migration from RTC/Jazz V2.0 on a test machine that is not the machine that the original repository is stored. Upon completing the migration, some users noticed that some of the links embedded withing existing work item descriptions were still pointing to the original (actual) server instead of the newly migrated test server and seem to hard coded that way. Is there a way to alleviate this issue in order to keep this from happening during the actual migration? Or is this simply something that will "fix itself" when the migration is performed on the actual server? Thank you for your help.
-Mike
4 answers
Hello,
I have completed a migration from RTC/Jazz V2.0 on a test machine that is not the machine that the original repository is stored. Upon completing the migration, some users noticed that some of the links embedded withing existing work item descriptions were still pointing to the original (actual) server instead of the newly migrated test server and seem to hard coded that way. Is there a way to alleviate this issue in order to keep this from happening during the actual migration? Or is this simply something that will "fix itself" when the migration is performed on the actual server? Thank you for your help.
-Mike
Hi Mike
What are the embedded links - where they of the form "defect #12" that became a hyperlink, or did people physically paste a web link "https://server:port/..."?
anthony
boydm wrote:
I think we ran into something similar in our testing of a migrated 2.0
database brought up in a different server:port location.
Go into your admin Advanced Properties page and do a search on the
original server name. Once we changed a reference there to the new
location our problem was fixed.
Hello,
I have completed a migration from RTC/Jazz V2.0 on a test machine that
is not the machine that the original repository is stored. Upon
completing the migration, some users noticed that some of the links
embedded withing existing work item descriptions were still pointing
to the original (actual) server instead of the newly migrated test
server and seem to hard coded that way. Is there a way to alleviate
this issue in order to keep this from happening during the actual
migration? Or is this simply something that will "fix
itself" when the migration is performed on the actual server?
Thank you for your help.
-Mike
I think we ran into something similar in our testing of a migrated 2.0
database brought up in a different server:port location.
Go into your admin Advanced Properties page and do a search on the
original server name. Once we changed a reference there to the new
location our problem was fixed.