From bb98484cecea3b34298abdda986281b3b42176e8 Mon Sep 17 00:00:00 2001 From: Andreas Gerler Date: Sun, 22 Dec 2024 13:31:45 +0100 Subject: [PATCH] update ox-jira Signed-off-by: Andreas Gerler --- .../ox-jira-20171001.916/ox-jira-autoloads.el | 15 - elpa/ox-jira-20171001.916/ox-jira-pkg.el | 2 - .../ox-jira-20241014.953/ox-jira-autoloads.el | 59 ++++ elpa/ox-jira-20241014.953/ox-jira-pkg.el | 10 + .../ox-jira.el | 301 +++++++++++------- elpa/ox-jira-readme.txt | 7 - 6 files changed, 257 insertions(+), 137 deletions(-) delete mode 100644 elpa/ox-jira-20171001.916/ox-jira-autoloads.el delete mode 100644 elpa/ox-jira-20171001.916/ox-jira-pkg.el create mode 100644 elpa/ox-jira-20241014.953/ox-jira-autoloads.el create mode 100644 elpa/ox-jira-20241014.953/ox-jira-pkg.el rename elpa/{ox-jira-20171001.916 => ox-jira-20241014.953}/ox-jira.el (75%) delete mode 100644 elpa/ox-jira-readme.txt diff --git a/elpa/ox-jira-20171001.916/ox-jira-autoloads.el b/elpa/ox-jira-20171001.916/ox-jira-autoloads.el deleted file mode 100644 index 5b0a8c6d..00000000 --- a/elpa/ox-jira-20171001.916/ox-jira-autoloads.el +++ /dev/null @@ -1,15 +0,0 @@ -;;; ox-jira-autoloads.el --- automatically extracted autoloads -;; -;;; Code: -(add-to-list 'load-path (directory-file-name (or (file-name-directory #$) (car load-path)))) - -;;;### (autoloads nil nil ("ox-jira.el") (23994 46391 581389 834000)) - -;;;*** - -;; Local Variables: -;; version-control: never -;; no-byte-compile: t -;; no-update-autoloads: t -;; End: -;;; ox-jira-autoloads.el ends here diff --git a/elpa/ox-jira-20171001.916/ox-jira-pkg.el b/elpa/ox-jira-20171001.916/ox-jira-pkg.el deleted file mode 100644 index cb5facd3..00000000 --- a/elpa/ox-jira-20171001.916/ox-jira-pkg.el +++ /dev/null @@ -1,2 +0,0 @@ -;;; -*- no-byte-compile: t -*- -(define-package "ox-jira" "20171001.916" "JIRA Backend for Org Export Engine" '((org "8.3")) :commit "db2ec528f46c9e611624ba28611c440a99bff255" :keywords '("outlines" "hypermedia" "wp") :authors '(("Stig Brautaset" . "stig@brautaset.org")) :maintainer '("Stig Brautaset" . "stig@brautaset.org") :url "https://github.com/stig/ox-jira.el") diff --git a/elpa/ox-jira-20241014.953/ox-jira-autoloads.el b/elpa/ox-jira-20241014.953/ox-jira-autoloads.el new file mode 100644 index 00000000..334f7319 --- /dev/null +++ b/elpa/ox-jira-20241014.953/ox-jira-autoloads.el @@ -0,0 +1,59 @@ +;;; ox-jira-autoloads.el --- automatically extracted autoloads (do not edit) -*- lexical-binding: t -*- +;; Generated by the `loaddefs-generate' function. + +;; This file is part of GNU Emacs. + +;;; Code: + +(add-to-list 'load-path (or (and load-file-name (directory-file-name (file-name-directory load-file-name))) (car load-path))) + + + +;;; Generated autoloads from ox-jira.el + +(autoload 'ox-jira-export-as-jira "ox-jira" "\ +Export current buffer as a Jira buffer. + +If narrowing is active in the current buffer, only export its +narrowed part. + +If a region is active, export that region. + +A non-nil optional argument ASYNC means the process should happen +asynchronously. The resulting buffer should be accessible +through the `org-export-stack' interface. + +When optional argument SUBTREEP is non-nil, export the sub-tree +at point, extracting information from the headline properties +first. + +When optional argument VISIBLE-ONLY is non-nil, don't export +contents of hidden elements. + +When optional argument BODY-ONLY is non-nil, omit header +stuff. (e.g. AUTHOR and TITLE.) + +EXT-PLIST, when provided, is a property list with external +parameters overriding Org default settings, but still inferior to +file-local settings. + +Export is done in a buffer named \"*Org JIRA Export*\", which +will be displayed when `org-export-show-temporary-export-buffer' +is non-nil. + +(fn &optional ASYNC SUBTREEP VISIBLE-ONLY BODY-ONLY EXT-PLIST)" t) +(register-definition-prefixes "ox-jira" '("ox-jira-")) + +;;; End of scraped data + +(provide 'ox-jira-autoloads) + +;; Local Variables: +;; version-control: never +;; no-byte-compile: t +;; no-update-autoloads: t +;; no-native-compile: t +;; coding: utf-8-emacs-unix +;; End: + +;;; ox-jira-autoloads.el ends here diff --git a/elpa/ox-jira-20241014.953/ox-jira-pkg.el b/elpa/ox-jira-20241014.953/ox-jira-pkg.el new file mode 100644 index 00000000..bd9c74bb --- /dev/null +++ b/elpa/ox-jira-20241014.953/ox-jira-pkg.el @@ -0,0 +1,10 @@ +;; -*- no-byte-compile: t; lexical-binding: nil -*- +(define-package "ox-jira" "20241014.953" + "JIRA Backend for Org Export Engine." + '((org "8.3")) + :url "https://github.com/stig/ox-jira.el" + :commit "6c2013088f442530cbd895abcf4a290c06e2beb0" + :revdesc "6c2013088f44" + :keywords '("outlines" "hypermedia" "wp") + :authors '(("Stig Brautaset" . "stig@brautaset.org")) + :maintainers '(("Stig Brautaset" . "stig@brautaset.org"))) diff --git a/elpa/ox-jira-20171001.916/ox-jira.el b/elpa/ox-jira-20241014.953/ox-jira.el similarity index 75% rename from elpa/ox-jira-20171001.916/ox-jira.el rename to elpa/ox-jira-20241014.953/ox-jira.el index 853cfbd6..221277a3 100644 --- a/elpa/ox-jira-20171001.916/ox-jira.el +++ b/elpa/ox-jira-20241014.953/ox-jira.el @@ -1,10 +1,10 @@ ;;; ox-jira.el --- JIRA Backend for Org Export Engine -;; Copyright (C) 2016 Stig Brautaset +;; Copyright (C) 2016-2020 Stig Brautaset ;; Author: Stig Brautaset -;; Version: 0.1-SNAPSHOT -;; Package-Version: 20171001.916 +;; Package-Version: 20241014.953 +;; Package-Revision: 6c2013088f44 ;; Keywords: outlines, hypermedia, wp ;; Homepage: https://github.com/stig/ox-jira.el ;; Package-Requires: ((org "8.3")) @@ -36,14 +36,13 @@ ;;; Code: -;; This is Cargo-culted from `ox-latex.el'` -(eval-when-compile (require 'cl)) +(eval-when-compile (require 'cl-lib)) (require 'ox) (require 'ox-publish) (require 'subr-x) - ;;; User Configurable Options + (defgroup ox-jira-export nil "Options specific to JIRA export back-end." :tag "Org Export JIRA" @@ -56,9 +55,59 @@ :group 'ox-export-jira :type '(integer)) +(defcustom ox-jira-src-supported-languages + '("actionscript" + "ada" + "applescript" + "c" + "c#" + "c++" + "css" + "erlang" + "go" + "groovy" + "html" + "haskell" + "json" + "java" + "javascript" + "lua" + "nyan" + "objc" + "php" + "perl" + "python" + "r" + "ruby" + "sql" + "scala" + "swift" + "visualbasic" + "xml" + "yaml" + "bash") + "Supported languages for syntax highlighting." + :group 'ox-export-jira + :type '(list)) + +;; For really long source snippets or sections of logfiles JIRA +;; supports showing a preview, and /collapsing/ the rest. How much to +;; preview before collapsing the rest is up to individual taste, so +;; let's make it configurable. + +(defcustom ox-jira-override-headline-offset nil + "Use this to override the (default) relative headline levels. + +If you want to have the headings *real* heading level in +the Jira output when you export a subsection, use `0' here. + +If you think the headings in Jira are too big by default, you +could set this to `2' to start headings at level 3." + :group 'ox-export-jira + :type 'integer) - ;;; Defining Backend + (org-export-define-backend 'jira '((babel-call . (lambda (&rest args) (ox-jira--not-implemented 'babel-call))) (body . (lambda (&rest args) (ox-jira--not-implemented 'body))) @@ -98,7 +147,7 @@ (planning . (lambda (&rest args) (ox-jira--not-implemented 'planning))) (property-drawer . (lambda (&rest args) (ox-jira--not-implemented 'property-drawer))) (quote-block . ox-jira-quote-block) - (radio-target . (lambda (&rest args) (ox-jira--not-implemented 'radio-target))) + (radio-target . ox-jira-radio-target) (section . ox-jira-section) (special-block . (lambda (&rest args) (ox-jira--not-implemented 'special-block))) (src-block . ox-jira-src-block) @@ -115,39 +164,37 @@ (verbatim . ox-jira-verbatim) (verse-block . (lambda (&rest args) (ox-jira--not-implemented 'verse-block)))) :filters-alist '((:filter-parse-tree . ox-jira-fix-multi-paragraph-items)) - :options-alist - '((:src-collapse-threshold nil nil ox-jira-src-collapse-threshold)) + :options-alist '((:src-collapse-threshold nil nil ox-jira-src-collapse-threshold)) :menu-entry '(?j "Export to JIRA" ((?j "As JIRA buffer" ox-jira-export-as-jira)))) ;;; Internal Helpers -;; Because I'm adding support for things as I find I need it rather than all -;; in one go, let's put a big fat red marker in for things we have not -;; implemented yet, to avoid missing it. -;; +;; Because I'm adding support for things as I find I need it rather than +;; all in one go, let's put a big fat red marker in for things we have +;; not implemented yet, to avoid missing it. + (defun ox-jira--not-implemented (element-type) "Replace anything we don't handle yet with a big red marker." (format "{color:red}Element of type '%s' not implemented!{color}" element-type)) -;; Super^script and sub_script I often want at the end of words, with no -;; whitespace immediately before it. Unfortunately JIRA doesn't support -;; that,so we have to fake it. This function makes simple text transforms -;; "embeddable" by preceding them with an empty anchor. This is admittedly a -;; bit of a hack, but I haven't found anything better. -;; +;; I often use super^script and sub_script at the end of words, with +;; no whitespace immediately before it. JIRA doesn't support that, so +;; we have to fake it. This function makes simple text transforms +;; "embeddable" by preceding them with an empty anchor. + (defun ox-jira--text-transform-embeddable (transform-char contents) (concat "{anchor}" transform-char contents transform-char)) ;;; Filters -;; Org support a single blank line between items in a list, but if we export -;; like that to JIRA format it will be interpreted as multiple consecutive -;; lists, which is never what I want. We can attempt to fix this by removing -;; the "post-blank" after a items (and paragraphs inside items) using a -;; filter. -;; +;; Org support a single blank line between items in a list, but if we +;; export like that JIRA interprets it as multiple consecutive lists; +;; which is never what I want. We can fix this by removing the +;; "post-blank" after =items= (and =paragraphs= inside =items=) using +;; a filter. + (defun ox-jira-fix-multi-paragraph-items (tree backend info) "Remove extra blank line between paragraphs in plain-list items. @@ -167,8 +214,8 @@ Assume BACKEND is `jira'." ;;; Transcode functions -;; These functions do the actual translation to JIRA format. For this section -;; I've used Atlassian's Text Formatting Notation Help page as a reference: +;; These functions do the actual translation to JIRA format. I used +;; Atlassian's Text Formatting Notation Help page as a reference, cf ;; https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all (defun ox-jira-bold (bold contents info) @@ -177,6 +224,7 @@ CONTENTS is the text with bold markup. INFO is a plist holding contextual information." (format "*%s*" contents)) +;; For CODE elements we cannot use the contents; it is always nil. (defun ox-jira-code (code _contents info) "Transcode a CODE object from Org to JIRA. CONTENTS is nil. INFO is a plist used as a communication @@ -199,8 +247,10 @@ information." (org-remove-indentation (org-element-property :value fixed-width)))) +;;;; Footnotes + ;; Footnotes have two parts: the reference, and the definition. -;; + (defun ox-jira--footnote-anchor (element) (let ((label (org-element-property :label element))) (replace-regexp-in-string ":" "" label))) @@ -226,20 +276,26 @@ information." (format "{anchor:fn%s}[^%s^|#fnr%s] %s" anchor ref anchor contents))) -;; Headlines are a little bit more complex. I'm not even attempting to support -;; TODO labels and meta-information, just the straight-up text. It would be -;; nice to support the six standard levels of headlines JIRA offers though. -;; -;; Since the headline level is _relative_ rather than absolute, if the -;; exporter sees a '** second level' heading before it's seen a '* first -;; level' then the '** second level' will think it's a top-level heading. -;; That's a bit weird, but there you go. -;; +;;;; Headline + +;; Headlines are a little bit more complex. I'm not even attempting to +;; support TODO labels and meta-information, just the straight-up +;; text. It would be nice to support the six standard levels of +;; headlines JIRA offers though. + +;; Since the headline level is /relative/ rather than absolute, if the +;; exporter sees a =** second level= heading before it's seen a =* +;; first level= then the =** second level= will think it's a top-level +;; heading. That's a bit weird, but there you go. + (defun ox-jira-headline (headline contents info) "Transcode a HEADLINE element from Org to JIRA. CONTENTS is the contents of the headline, as a string. INFO is the plist used as a communication channel." - (let* ((level (org-export-get-relative-level headline info)) + (let* ((headline-info (if (eql ox-jira-override-headline-offset nil) + info + (plist-put nil :headline-offset ox-jira-override-headline-offset))) + (level (org-export-get-relative-level headline headline-info)) (title (org-export-data-with-backend (org-element-property :title headline) 'jira info)) @@ -271,22 +327,25 @@ CONTENTS is the text with italic markup. INFO is a plist holding contextual information." (format "_%s_" contents)) -;; A list item. The JIRA format for nested lists follows. (You can also mix -;; ordered and unordered lists.) -;; -;; * item -;; ** sub-item -;; ** sub-item 2 -;; * item 2 -;; -;; The item element itself does not know what type it is: that is an attribute -;; of its parent, a plain-list element. We need to walk the path of -;; alternating plain-list and item nodes until there are no more, and extract -;; their type. The type list is used to create a bullet string. -;; -;; JIRA doesn't really have support for definition lists, so we fake it with a -;; bullet list and some bold text for the term. -;; +;;;; List item + +;; A list item. The JIRA format for nested lists follows. (You can +;; also mix ordered and unordered lists.) + +;; : * item +;; : ** sub-item +;; : ** sub-item 2 +;; : * item 2 + +;; The item element itself does not know what type it is: that is an +;; attribute of its parent, a plain-list element. We need to walk the +;; path of alternating plain-list and item nodes until there are no +;; more, and extract their type. The type list is used to create a +;; bullet string. + +;; JIRA doesn't really have support for definition lists, so we fake +;; it with a bullet list and some bold text for the term. + (defun ox-jira--list-type-path (item) (when (and item (eq 'item (org-element-type item))) (let* ((list (org-element-property :parent item)) @@ -321,10 +380,16 @@ contextual information." (format "*%s*: " tag)) contents))) -;; JIRA supports many types of links. I don't expect we support them all, but -;; we must make a token effort. A lot of this code is cribbed from -;; `ox-latex.el'. -;; +(defun ox-jira-radio-target (radio-target contents info) + "Transcode a RADIO-TARGET object from Org to JIRA. +CONTENTS is nil. INFO is a plist holding contextual information." + (let ((value (org-element-property :value radio-target))) + (format "{anchor:%s}" value))) + +;; JIRA supports many types of links. I don't expect to support them +;; all, but we must make a token effort. A lot of this code is cribbed +;; from =ox-latex.el=. + (defun ox-jira-link (link desc info) "Transcode a LINK object from Org to JIRA. @@ -337,8 +402,17 @@ INFO is a plist holding contextual information. See (path (cond ((member type '("http" "https" "ftp" "mailto" "doi")) (concat type ":" raw-path)) + ((string-prefix-p "~accountid" raw-path) + raw-path) ((string= type "file") (org-export-file-uri raw-path)) + ((string= type "custom-id") + (if desc (concat "#" desc) (concat "#" raw-path))) + ((string-prefix-p "*" raw-path) + (concat "#" (seq-subseq raw-path 1))) + ((string= type "radio") + (concat "#" raw-path)) + ((org-export-custom-protocol-maybe link desc 'jira info)) (t raw-path)))) (cond ;; Link with description @@ -360,15 +434,10 @@ CONTENTS is nil. INFO is a plist used as a communication channel." (format "{{%s}}" (org-element-property :value verbatim))) -;; One of the most annoying things about JIRA markup is the way it doesn't -;; reflow text properly, so any linebreaks become hard linebreaks in the -;; rendered output. Let's fix that! -;; -;; What we need to do is replace any *internal* newlines (i.e. any not at the -;; end of the string) with a space. Regexes to the rescue! I used the -;; following reference to help me with this function: -;; https://www.gnu.org/software/emacs/manual/html_node/elisp/Regexp-Backslash.html#Regexp-Backslash - +;; One of the most annoying aspects of JIRA markup is its broken +;; handling of line breaks; any newlines in the source becomes hard +;; linebreaks in the rendered output. We need to replace /internal/ +;; newlines (i.e. any not at the end of the string) with a space. (defun ox-jira-paragraph (paragraph contents info) "Transcode a PARAGRAPH element from Org to JIRA. @@ -376,22 +445,21 @@ CONTENTS is the contents of the paragraph, as a string. INFO is the plist used as a communication channel." (replace-regexp-in-string "\n\\([^\']\\)" " \\1" contents)) -;; I make a lot of lists. Let's make sure we handle them! This is very simple, -;; as in the JIRA format all the logic is actually _for each item_ in the -;; list. -;; +;; Lists are simple to support since all the complexity is in the code +;; for list item. + (defun ox-jira-plain-list (plain-list contents info) "Transcode PLAIN-LIST from Org to JIRA. CONTENTS is the text with plain-list markup. INFO is a plist holding contextual information." contents) -;; This is text with no markup, but we have to escape certain characters to -;; avoid tripping up JIRA. In particular: -;; +;; This is text with no markup, but we have to escape certain +;; characters to avoid tripping up JIRA. In particular: + ;; - ={= :: Introduces macros ;; - =[= :: Introduces links -;; + (defun ox-jira-plain-text (text info) "Transcode TEXT from Org to JIRA. TEXT is the string to transcode. INFO is a plist holding @@ -399,11 +467,9 @@ contextual information." (replace-regexp-in-string "\\([[{]\\)" '(lambda (p) (format "\\\\%s" p)) text)) - -;; Paragraphs are grouped into sections. I've not found any mention in the Org -;; documentation, but it appears to be essential for any export to happen. -;; I've essentially cribbed this from `ox-latex.el`. -;; +;; Paragraphs are grouped into sections. I've not found any mention in +;; the Org documentation, but it appears to be essential for any +;; export to happen. I've essentially cribbed this from =ox-latex.el=. (defun ox-jira-section (section contents info) "Transcode a SECTION element from Org to JIRA. @@ -411,11 +477,10 @@ CONTENTS is the contents of the section, as a string. INFO is the plist used as a communication channel." contents) -;; JIRA supports formatting for these languages: actionscript, html, -;; java, javascript, sql, xhtml, xml. If none of them fits, we can use 'none', -;; or leave out the language altogether, which I imagine will be a bit like +;; If language is not member of =ox-jira-src-supported-languages=, +;; =none=, will be used which I imagine will be a bit like ;; ={noformat}=. -;; + (defun ox-jira-src-block (src-block contents info) "Transcode a SRC-BLOCK element from Org to Jira. CONTENTS holds the contents of the src-block. INFO is a plist holding @@ -423,13 +488,13 @@ contextual information." (when (org-string-nw-p (org-element-property :value src-block)) (let* ((title (apply #'concat (org-export-get-caption src-block))) (lang (org-element-property :language src-block)) - (lang (if (member lang '("actionscript" "html" "java" "javascript" "sql" "xhtml" "xml")) lang "none")) + (lang (if (member lang ox-jira-src-supported-languages) lang "none")) (code (org-export-format-code-default src-block info)) (collapse (if (< (plist-get info :src-collapse-threshold) (org-count-lines code)) "true" "false"))) (concat - (format "{code:language=%s}" lang) + (format "{code:title=%s|language=%s|collapse=%s}" title lang collapse) code "{code}")))) @@ -445,34 +510,36 @@ CONTENTS is the text with superscript markup. INFO is a plist holding contextual information." (ox-jira--text-transform-embeddable "^" contents)) +;;;; Tables + +;; Org's table editor is one of the many reasons to use Org; it is +;; excellent. Org and JIRA's tables are quite similar. Where Org marks +;; tables up like this: + +;; : | Name | Score | +;; : |--------+-------| +;; : | Ashley | 2 | +;; : | Alex | 3 | -;; Org's table editor is one of the many reasons to use Org. It is excellent. -;; Org and JIRA's tables are quite similar. Where Org marks tables up like -;; this: -;; -;; | Name | Score | -;; |--------+-------| -;; | Ashley | 2 | -;; | Alex | 3 | -;; ;; Jira uses the following format: -;; -;; || Name || Score || -;; | Ashley | 2 | -;; | Alex | 3 | -;; -;; Tables are complex beasts. I only hope to support very simple ones. Looks -;; like most of the logic will live in the row and cell transcoding functions. -;; + +;; : || Name || Score || +;; : | Ashley | 2 | +;; : | Alex | 3 | + +;; Tables are complex beasts. I only hope to support simple ones. +;; Looks like most of the logic will live in the row and cell +;; transcoding functions. + (defun ox-jira-table (table contents info) "Transcode a TABLE element from Org to JIRA. CONTENTS holds the contents of the table. INFO is a plist holding contextual information." contents) -;; We only want to output =standard= rows, not horizontal lines. I'm not sure -;; if detection of header rows belongs here or in the cells. -;; +;; We only want to output =standard= rows, not horizontal lines. I'm +;; not sure if detection of header rows belong here or in the cells. + (defun ox-jira-table-row (table-row contents info) "Transcode a TABLE-ROW element from Org to JIRA. CONTENTS holds the contents of the table-row. INFO is a plist holding @@ -480,10 +547,11 @@ contextual information." (when (eq 'standard (org-element-property :type table-row)) (format "%s\n" contents))) -;; The cell itself does not know if it is a header cell or not, so we have to -;; ask its containing row if it is the first row, and the table if it has a -;; header row at all. If those things are true, make the cell a header cell. -;; +;; The cell itself does not know if it is a header cell or not, so we +;; have to ask its containing row if it is the first row, and the +;; table if it has a header row at all. If those things are true, make +;; the cell a header cell. + (defun ox-jira-table-cell (table-cell contents info) "Transcode a TABLE-CELL element from Org to JIRA. CONTENTS holds the contents of the table-cell. INFO is a plist holding @@ -498,12 +566,19 @@ contextual information." (if (org-export-last-sibling-p table-cell info) sep "")))) ;; This is updated to show progress of subsequent list of check boxes. -;; + (defun ox-jira-statistics-cookie (statistics-cookie _contents _info) "Transcode a STATISTICS-COOKIE object from Org to JIRA. CONTENTS is nil. INFO is a plist holding contextual information." (format "\\%s" (org-element-property :value statistics-cookie))) +;; JIRA call this "deleted text". In my opinion this is rather silly +;; because it is obviously there. Org is at least logical in calling +;; it for what it is. I suppose JIRA is trying to be semantic here, +;; but outside a diff you rather want to look in the revision log for +;; deleted text rather than have it clutter up things. Still, it's +;; simple to support, so we might as well do it. + (defun ox-jira-strike-through (strike-through contents info) "Transcode STRIKE-THROUGH from Org to JIRA. CONTENTS is the text with strike-through markup. INFO is a plist holding @@ -516,7 +591,6 @@ CONTENTS holds the contents of the block. INFO is a plist holding contextual information." (format "{quote}\n%s{quote}" contents)) - (defun ox-jira-timestamp (timestamp _contents info) "Transcode a TIMESTAMP object from Org to JIRA. CONTENTS is nil. INFO is a plist holding contextual information." @@ -527,6 +601,7 @@ CONTENTS is nil. INFO is a plist holding contextual information." (otherwise "_%s_")))) (format fmt value))) +;;;###autoload (defun ox-jira-export-as-jira (&optional async subtreep visible-only body-only ext-plist) "Export current buffer as a Jira buffer. diff --git a/elpa/ox-jira-readme.txt b/elpa/ox-jira-readme.txt deleted file mode 100644 index aadde68f..00000000 --- a/elpa/ox-jira-readme.txt +++ /dev/null @@ -1,7 +0,0 @@ -This module plugs into the regular Org Export Engine and transforms Org -files to JIRA markup for pasting into JIRA tickets & comments. - -In an Org buffer, hit `C-c C-e j j' to bring up *Org Export Dispatcher* -and export it as a JIRA buffer. I usually use `C-x h' to mark the whole -buffer, then `M-w' to save it to the kill ring (and global pasteboard) for -pasting into JIRA issues. -- 2.47.3