-
Suggestion
-
Resolution: Unresolved
-
None
-
8
-
19
-
Summary
- Currently, you can only trigger the smart link if you type a whitespace or line break, but there are certain scenarios where these characters will not be used, and the comment will be submitted without the smart link.
Examples
- "Maybe this is related to ISSUE-2020" (Issue at the end of the sentence, comment submitted)
- "Check the resolution on ISSUE-2020, same symptoms." (A comma after the issue key)
- "This seems to be the same as ISSUE-2020." (Sentence ends with a dot)
- Typing "This seems to be the same as ISSUE-2020." and then immediately saving the issue (i.e. not adding whitespace or a line break)
Additional notes
- The old issue view would process the smart link after the comment is submitted, so it wasn't a problem, but for the sake of parity, these scenarios should be handled as well on the new issue view.
Workaround
Use English to Yoda translatorsUse a whitespace to process the smart link or line break before submitting the comment, the line break will be ignored.
- is duplicated by
-
JRACLOUD-76524 Pasting issue keys on the new view will not create smart link
-
- Closed
-
- is related to
-
JRACLOUD-76619 Set a default option to display links in comments/description
- Closed
-
JRACLOUD-77107 Disable Smart Links / link previews
- Closed
- relates to
-
JRACLOUD-77611 Hitting enter after an Issue Key will not transform it into a link
-
- Closed
-
-
JRACLOUD-37224 Allow disabling of issue key links
- Gathering Interest
We have users who routinely as part of their work copy in lists or tables of issue references from external sources into Jira issues. Having to go through the pasted data and force link creation for each one by adding and removing a space (or similar) rather than just having the links be created is quite irritating.