Skip to main content

This plugin provides two latex features for Jirafs –

  • Automatically conversion of latex documents into PDF documents before uploading the PDF to JIRA.

  • A {latex} macro block you can use in comments and ticket descriptions for embedding inline images or PDFs into your text.

Installation

  1. Install from PIP:

    pip install jirafs-latex
  2. Enable for a ticket folder:

    jirafs plugins --enable=latex

Note that you can globally enable this (or any) plugin by adding the --global flag to the above command:

jirafs plugins --global --enable=latex

Requirements

  • Requires xelatex.

Using the Automatic Latex Compiler

Simply place a file with a .tex extension in your ticket folder. It’ll be compiled into a PDF automatically, and the PDF will be uploaded to JIRA (not the .tex file) next time you push changes to JIRA.

Using the {latex} Macro Block

Enter a latex block like so:

{latex:name=somefilename.pdf}
\documentclass{article}
\usepackage{graphicx}

\begin{document}

\title{Introduction to \LaTeX{}}
\author{Author's Name}

\maketitle

\begin{abstract}
The abstract text goes here.
\end{abstract}

\section{Introduction}
Here is the text of your introduction.

\begin{equation}
    \label{simple_equation}
    \alpha = \sqrt{ \beta }
\end{equation}

\subsection{Subsection Heading Here}
Write your subsection text here.

\begin{figure}
    \centering
    \includegraphics[width=3.0in]{myfigure}
    \caption{Simulation Results}
    \label{simulationfigure}
\end{figure}

\section{Conclusion}
Write your conclusion here.

\end{document}
{latex}

The above will be replaced with inline image JIRA markup (in this case, !somefilename.pdf!) when submitting these changes to JIRA.

You must specify a name parameter in your opening {latex} tag; that’s the filename that will be uploaded to JIRA next time you submit changes. Also, note that if you have the standalone latex plugin installed and use it to convert your latex documents into PNG images instead, you should specify a filename ending in png in your name parameter.

This is probably not important to you, but if you’re curious about how this works: what is happening here is the plugin writes your latex content to a file, then asks xelatex to compile your document, then once that process has completed, all files except the one matching the name you’ve submitted are deleted. After this point, everything works exactly as it does when you’re uploading a normal file.

Metadata

Release files for jirafs-latex 2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jirafs-latex 2.0
File Size Uploaded
jirafs-latex-2.0.tar.gz 4.0 kB Details

Release files / jirafs-latex-2.0.tar.gz

Download URL jirafs-latex-2.0.tar.gz
Size 4.0 kB
Tags Source
SHA-256 checksum
How to use checksums
3e03b7ded8f7ac59d149b148c173380094d99080c18d884ef38481b08570c010
BLAKE2b-256 checksum
How to use checksums
581cb15d66419582bade8f907b0e11c7c90119a5ff83f831d15d0e7278520f12
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release history Release notifications | RSS feed

This release

2.0 This release

1 release file

1.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page