-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
Below is actually a bug, not a suggestion, but since creating bugs directly has been disabled (with poor user feedback) and I'm not entitled to contact support, here we go:
Certain links (ones that look like Jira issue keys?) seem to confuse Bitbucket's markdown parser when the reference link style is used:
- [[TEST-1]] Test 1 [TEST-1]: https://translate.google.com/?text=one - [[TEST-2]] Test 2 [TEST-2]: https://translate.google.com/?text=two - [[TEST-3]] Test 3 [TEST-3]: https://translate.google.com/?text=three
Expected:
- [TEST-1] Test 1
- [TEST-2] Test 2
- [TEST-3] Test 3
Actual:
- [TEST-1] Test 1
- [TEST-1] Test 2
- [TEST-2] Test 3
Since we specifically want to create markdown that works in both PhpStorm, Bitbucket and other viewers, using plain Jira links is not an option.
Haven't checked whether other link styles (e.g. inline) work correctly. They might, but that's not a good alternative for us since those cannot be shared/reused within the same document.
The problem does not occur with different (e.g. lowercase) link keys, e.g. test-1, test-2, test-3.
- relates to
-
BSERV-10936 Using something that looks like a Jira issue key in a link label or shortcut renders wrong markup
- Gathering Impact