automatic hyperlinking during import

One approach would be to run a quick editing script on your csv file to
modify the description/comment fields, so that the description/comment
fields have been adjusted to no longer look like work item references.

Cheers,
Geoff

On 9/15/2011 9:53 AM, dtownsmr wrote:

Is there anyway to disable the hyperlinking during the import process?


We're migrating from one RTC system to another and have export the
workitems into a csv file and when we import the workitems into the
new system the auto hyperlinking is creating bogus references...and
it's not even confined to our project area...so we're polluting work
items in other teams project areas.

I'm hoping there's some way to tag descriptions/comments and not have
the hyperlinking occur.

Thanks in advance.

One approach would be to run a quick editing script on your csv file to modify the description/comment fields, so that the description/comment fields have been adjusted to no longer look like work item references.

Cheers,
Geoff

Thanks Geoff, have thought about doing that but I have yet to find any documentation on what the hyper-link code keys off of. I'd like it to be robust and not just based on the examples I can happen to run across. It's not very reasonable to check all 3500 of our work items.

I assume you are referring to the "mention" links.
Those look for:
- any string in a comment or description that matches the name of the
work item type that is followed by an integer (e.g. "defect 23", if you
have a "defect" work item type.
- any string declared in your process configuration as an "alias" for a
work item type.

Cheers,
Geoff

On 9/15/2011 1:53 PM, dtownsmr wrote:

gmclemmwrote:
One approach would be to run a quick editing script on your csv file
to modify the description/comment fields, so that the
description/comment fields have been adjusted to no longer look like
work item references.

Cheers,
Geoff

Thanks Geoff, have thought about doing that but I have yet to find any
documentation on what the hyper-link code keys off of. I'd like it to
be robust and not just based on the examples I can happen to run
across. It's not very reasonable to check all 3500 of our work items.

I assume you are referring to the "mention" links.
Those look for:
- any string in a comment or description that matches the name of the
work item type that is followed by an integer (e.g. "defect 23", if you
have a "defect" work item type.
- any string declared in your process configuration as an "alias" for a
work item type.

Cheers,
Geoff

On 9/15/2011 1:53 PM, dtownsmr wrote:

gmclemmwrote:
One approach would be to run a quick editing script on your csv file
to modify the description/comment fields, so that the
description/comment fields have been adjusted to no longer look like
work item references.

Cheers,
Geoff

Thanks Geoff, have thought about doing that but I have yet to find any
documentation on what the hyper-link code keys off of. I'd like it to
be robust and not just based on the examples I can happen to run
across. It's not very reasonable to check all 3500 of our work items.

It also seems to create a link for the text of a work item followed by the number in parens. ex.

PMR tabs loose focus within Retain Viewer on an inconsistent basis (16584)

So I assumed there might be others but maybe you're right and it is that simple.

Those work item links of the form "summary (id)" are created when you
select the "copy URL" function on a work item, and then paste that into
the Description or Comment field.

It's some kind of rich text ... I don't know exactly how that is
implemented (perhaps someone could comment on that?).

Cheers,
Geoff



On 9/16/2011 3:38 PM, dtownsmr wrote:

gmclemmwrote:
I assume you are referring to the "mention" links.
Those look for:
- any string in a comment or description that matches the name of
the
work item type that is followed by an integer (e.g. "defect
23", if you
have a "defect" work item type.
- any string declared in your process configuration as an
"alias" for a
work item type.

Cheers,
Geoff

On 9/15/2011 1:53 PM, dtownsmr wrote:
gmclemmwrote:
One approach would be to run a quick editing script on your csv
file
to modify the description/comment fields, so that the
description/comment fields have been adjusted to no longer look
like
work item references.

Cheers,
Geoff

Thanks Geoff, have thought about doing that but I have yet to find
any
documentation on what the hyper-link code keys off of. I'd like it
to
be robust and not just based on the examples I can happen to run
across. It's not very reasonable to check all 3500 of our work
items.

It also seems to create a link for the text of a work item followed by
the number in parens. ex.

PMR tabs loose focus within Retain Viewer on an inconsistent basis
(16584)

So I assumed there might be others but maybe you're right and it is
that simple.