-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jira reader: support anchors and anchor links #6407
Comments
I tried with both "incorrect" versions, and neither produced a link for me in Jira. I don't think we can do any better than what we do now. Does it work for you, and which Jira version are you using? |
According to the documentation, the anchor syntax is as follows (and I can roughly confirm in jira v8.5.1):
so this should produce the following HTML (modulo some paragraphs):
funnily,
|
Ah, right! We are not actually parsing links to anchors at all! Fixing it now. Thanks! |
Which, btw, means that the current cloud jira has a bug. Anchor links are only parsed in the preview, but fail to render in the actual ticket 🤔 |
thanks! and yes, we're not parsing anchors either :)
yeah, I observed something similar. I think the feature only really works in confluence, but they use the same parser, so the syntax is valid in jira tickets, but the anchors just get stripped on save... or something like that :) |
Parse links to anchors and treat them like normal links. See: jgm/pandoc#6407
Parse links to anchors and treat them like normal links. See: jgm/pandoc#6407
Could you give an example for that? It seems to work ok from what I can tell. |
ah yes, anchors actually work.. (I tested on an older version..) nice! |
@tarleb Sorry I don't want to hijack this Issue but I see it most fitting here: We have a special case where the link text in Jira Markup contains square brackets, e.g. Unfortunately, this is converted to the following HTML: <p>Please refer to [[3]|#appendix]</p> instead of expected: <p>Please refer to <a href="#appendix">[3]</a></p> |
@0xDAFE please open a new issue for this, ideally with a fully reproducible example and description of the Jira version which you are using. I entered the above into Jira cloud, but got the same output as produced by pandoc. |
This Pandoc markdown produces the correct Jira markdown.
This Pandoc markdown produces the correct Jira markdown.
This Jira markdown produces the incorrect Pandoc markdown.
This Jira markdown produces the incorrect Pandoc markdown.
@tarleb Do you agree regarding my observations on this?
The text was updated successfully, but these errors were encountered: