Is there a way to make a link to an issue based off of a number manually entered by a user?

Hi Tracy,

If you could instead have users enter the the ID (vs Reference Number; and update all your old data manually or with our Excel Updater solution), it would be quite easy to then format it in a calculated parameter into a link. You could also (instead) paste the URL of the related issue directly in the URL of the new Issue, which would allow you to then navigate between them (again, old data updates required).

Alternatively, if the previous Issues are also within the same project, it might be possible to iterate though them to find the Reference Number that matches...and perhaps even display a properly formatted link...but the last time I tried something similar, I don't believe I was able to make the link "clickable".

Regards,

Doug

Hi Tracy,

The reference number and the long GUID are interchangeable in the URL format. So,

https://domain.my.workfront.com/issue/view?ID=60cb84390034cb84390034cb84390034

=

https://domain.my.workfront.com/issue/view?ID=150819

You can just build a calculated field in your form that references your text input field. (Below example presumes the name of the field in which you input the ref# is "Prior Request Ref Number")

Field name:

URL Referenced Request

Calculation:

IF(ISBLANK(Prior Request Ref Number),"",CONCAT("https://domain.my.workfront.com/issue/view?ID=",Prior Request Ref Number))

You could also do the above in a calculated column in a view, but if you add the calc field to your form, that will enable the below text mode in a view that will display a short, clickable link in a column:

valueexpression=IF(ISBLANK({DE:URL Referenced Request}),"","Open")

link.url=customDataLabelsAsString(URL Referenced Request)

textmode=true

valueformat=HTML

displayname=Open Linked Request

If someone enters something like "I don't know" in the Prior Request Ref Number field, a hyperlink will still get generated but obviously it won't work and the users will assume the link is broken before they consider someone entered a bad value. (Hopefully the data format is set to Number, but even then some users may enter "0000" - if there's a way to break it, they will find it)

To mitigate against bad values in that field, I would put two columns in my view: one as a "read-only" column displaying the value that was entered in Prior Request Ref Number, so users can validate that a value was entered and that it looks normal. Then, a second column using the above text mode to make it easy to open.

I stand happily corrected Bill,

That is a superb solution. Thank you for educating me!

Regards,

Doug