Marek Parfianowicz added a comment - 05/Oct/2018 11:33 AM Atlassian Update – 5 October 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Regards Marek Parfianowicz Fisheye/Crucible TL

Partha added a comment - 29/Sep/2008 4:56 AM One of our customers has found a workaround for this (based on FreeMark Regexes and supplied an example below: 2. For the text replacement there is function "matches" and "r" flag for the replace. So we've done it the following way with "matches": [#attempt] [#assign comment=commentFormatter.format(repcfg, cs.comment)] [#if comment?matches(".*#[\\d]{3,7}[^\\d].*") ] <br> [#assign cases=comment?matches("#([\\d]{3,7})[^\\d]")] [#list cases as case] <a href="URL://${case?groups[1]}">#${case?groups[1]}</a> [/#list] [/#if] [#recover] Failed to process cases [/#attempt] For some reasons it doesn't work for cs.comment, only for formatted one.