{"action":"opened","issue":{"url":"https://api.github.com/repos/serenity-bdd/serenity-core/issues/346","repository_url":"https://api.github.com/repos/serenity-bdd/serenity-core","labels_url":"https://api.github.com/repos/serenity-bdd/serenity-core/issues/346/labels{/name}","comments_url":"https://api.github.com/repos/serenity-bdd/serenity-core/issues/346/comments","events_url":"https://api.github.com/repos/serenity-bdd/serenity-core/issues/346/events","html_url":"https://github.com/serenity-bdd/serenity-core/issues/346","id":139599755,"number":346,"title":"jira.url property breaks links to scenario details in reports.","user":{"login":"dmitriy-grablyov","id":17745958,"avatar_url":"https://avatars.githubusercontent.com/u/17745958?v=3","gravatar_id":"","url":"https://api.github.com/users/dmitriy-grablyov","html_url":"https://github.com/dmitriy-grablyov","followers_url":"https://api.github.com/users/dmitriy-grablyov/followers","following_url":"https://api.github.com/users/dmitriy-grablyov/following{/other_user}","gists_url":"https://api.github.com/users/dmitriy-grablyov/gists{/gist_id}","starred_url":"https://api.github.com/users/dmitriy-grablyov/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dmitriy-grablyov/subscriptions","organizations_url":"https://api.github.com/users/dmitriy-grablyov/orgs","repos_url":"https://api.github.com/users/dmitriy-grablyov/repos","events_url":"https://api.github.com/users/dmitriy-grablyov/events{/privacy}","received_events_url":"https://api.github.com/users/dmitriy-grablyov/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-09T14:56:46Z","updated_at":"2016-03-09T14:56:46Z","closed_at":null,"body":"This problem is observed when using serenity-core with serenity-jbehave  and writing BDD stories\r\n\r\nFirst of all there is an issue that reporter tries to mark as ticket number Everything matching jira url pattern.\r\nFor example, even if I set jira.project=OR it will parse as ticket key both OR-17 and TC-OR-1721-1 (last one we use just as testcase code which is nothing common with issue tracking).\r\n\r\nAnd the problem comes with the usage of jira.url property\r\nLet's say we have a scenario named \"TC-OR-1010-1 Do something\" which is linked by issue metatag to ticket OR-1010. In this case in reports the scenario will be described as:\r\n`\r\n<td class=\"SUCCESS-text sorting_1\">\r\n                                <a href=\"5330538ab89c976e1a23ff87461d24005cac76462763e0d5ca39c58f526edf2b.html\" class=\"ellipsis\" title=\"\">\r\n                                    TC-OR-1010-1 Do something (OR-1010, TC-OR-1010-1)\r\n                                </a>\r\n                            </td>\r\n`\r\n\r\nEverything here is just a text and this text is clickable since it is whole under a tag\r\n\r\nif I specify jira.url parameter - it will try to make every key a link to jira and html goes this way:\r\n\r\n`\r\n<td class=\"SUCCESS-text sorting_1\">\r\n                                <a href=\"214eb7b738ec5c9289c043e797caeb60cf1ae342e0275ee14cbf87230a95afd9.html\" class=\"ellipsis\" title=\"\">\r\n                                    </a><a target=\"_blank\" href=\"https://jira.net/browse/TC-OR-1010-1\">TC-OR-1010-1</a> Do something (<a target=\"_blank\" href=\"https://jira.net/browse/OR-1010\">OR-1010</a>, <a target=\"_blank\" href=\"https://jira.net/browse/TC-OR-1010-1\">TC-OR-1010-1</a>)\r\n                            </td>\r\n`\r\n\r\nIn this case text is no more clickable and scenario details are no more accessible because original a tag is closed immediately without any text I can click on.\r\n\r\nTo reproduce this issue just create a dummy scenario containing some jira-like key at the beginning of scenario name. Execute this test setting some valid url for jira.url in serenity.properties"}}