Jim Murray

Thanks for the speedy reply Ulf, I tend to use the search from the top menu bar and completely forgot about the workspace search buttons. It makes sense given the STATUS field is an enumeration. jim

Would it be possible to enable STATUS as a searchable field, so that I can search only "OPEN" issues etc.?

thanks Ulf. its more about the false positives than not eventually finding a hit you actually wanted. with technical and IT text its not unusual to have compound words for object names etc eg 'This_is_my_very_special_routine_name'. ( a lot of older source code does not use bumpy or camel case for routine names etc, and if maintaining issues on that code base, hyphenated and underscored words are common) the only hit I would be interested in would be when the whole compound word/phrase matches, not...

thanks Ulf. its more about the false positives than not eventually finding a hit you actually wanted. with technical and IT text its not unusual to have compound words for object names etc eg 'This_is_my_very_special_routine_name'. ( a lot of older source code does not use bumpy or camel case for routine names etc, and if maintaining issues on that code base, hypenated and underscored words are common) the only hit I would be interested in would be when the whole compound word/phrase matches, not...

hi Ulf, is there any easy way to change the Lucene Analyzer used by Jtrac to allow underscores in words ? The standard analyzer will word-break at underscores, but what if you wish to maintain words containing underscores? thanks jim

much appreciated Ulf. I had some problems building a snapshot of the sources , I probably have not got my settings correct to handle the different language resources as Maven kept bombing, but for my test I removed all but English and got a good rebuild. So now after enabling HTML I have tested some simple HTML additions and they looks fine, thanks again for your speedy responses jim

Thanks Ulf, yes I wondered about the security aspect of raw html but in the case where JTrac is used solely inside a firewall and has no general public access, this would be a well confined risk. Perhaps 1/. It should be disabled by default and only enabled by administrator as you state 2/. It should be selectable , for example the administrator may wish to enable for wiki but not for issue detail/comment fields etc. 3/. If you wanted more work , you could parse and only allow a subset of html tags....

Thanks for the reply Ulf, sorry for my delay I didnt get email ping (coz I forgot to subscribe!) Section 4.6 of the CommonMark specs https://spec.commonmark.org/0.30/#html-blocks https://spec.commonmark.org/0.30/#html-blocks not sure of the code base you build with, perhaps the feature has a spec but no implementation as yet,