Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

Site Extensions

    +

    Test and document your Asciidoctor.js or Antora extensions here.

    Inline JIRA macro

    Usage

    == Fixed issues:

* jira:JSCBC-1234[]: reversed the polarity of the neutron flow
* jira:AV-2345[]: frobnicated the gostaks
* jira:DOC-999[The dreaded DOC-999 ticket...]: implemented jira macro
    antora-playbook.yml
    asciidoc:
  attributes:
    # ...
    url-issues: https://issues.couchbase.com/browse
    url-issues-JSCBC: https://issues.couchbase.com/browse
    url-issues-AV: https://couchbasecloud.atlassian.net/browse
  extensions:
  # ...
  - ./lib/inline-jira-macro.js

    Output

    Fixed issues:

    • jira:JSCBC-1234[]: reversed the polarity of the neutron flow

    • jira:AV-2345[]: frobnicated the gostaks

    • jira:DOC-999[The dreaded DOC-999 ticket…​]: implemented jira macro

    Markdown Block

    [markdown]
--
Filter some text with [Markdown](https://commonmark.org/help/) syntax.
--

    Results in:

    Filter some text with [Markdown](https://commonmark.org/help/) syntax.

    This is not implemented with a full Markdown parser. See issue with a link to the "naive series of regexes" used as starting point.

    (And note that we use Open structural context, with -- delimiters, and headings don’t work inside these.)

    This feature is intended for handling OpenAPI specs, which can contain Markdown, however openapi-generator has poor Asciidoc handling, so instead we add the block delimiters in the template, and let the block filter handle it.