The Jira Issue plugin enables seamless integration between Obsidian and Atlassian Jira, allowing users to track, search, and display Jira issues directly within their notes. With support for multiple components, including detailed issue tracking, custom Jira queries, issue counts, and inline issue tagging, users can efficiently manage their tasks and monitor project statuses. The plugin provides flexible markdown syntax to embed Jira-related data, offering visualization options like tables and inline summaries.

The Agile Task Notes plugin allows users to integrate task management systems like Jira and Azure DevOps into Obsidian, creating a seamless workflow for managing tasks and notes. It generates a local Kanban board featuring tasks assigned to you, enabling easy navigation within Obsidian. Each task is automatically converted into a dedicated note, where users can add personalized notes and to-do lists. The plugin also provides customizable templates for task notes, making it adaptable to individual workflows.

The Jira Linker plugin enhances your Obsidian experience by enabling seamless integration with Jira. It provides commands to quickly generate web-based URLs or local file links for Jira issues, supporting multiple Jira instances. Users can configure their Jira instance URLs, set a local directory as the root for issue-related files, and customize the default 'main' file name. The plugin allows you to highlight a Jira issue in the editor and link it with a simple command, or input an issue identifier manually. This functionality streamlines access to Jira-related information within your notes.

The Markdown to Jira Converter plugin enables users to seamlessly convert Markdown notes or selected text into Jira markup and vice versa. This plugin supports two main operations: converting the entire note or a selected portion of text into Jira format, and converting Jira markup back into Markdown. It is designed to simplify the workflow for users who work with both Obsidian and Jira by ensuring that their notes can be easily transferred between the two platforms. The plugin supports handling callouts and images, and has undergone improvements such as enhanced line break handling and bug fixes. It also allows for easy conversion of multi-line bullet lists and images.

The Incremental ID plugin provides a convenient way to generate unique IDs for your Obsidian notes. With this plugin, you can declare a prefix of your choice (such as "DN" for daily notes) and then insert incremental numbers into your notes using a simple command or template code. This feature is particularly useful when working with kanban boards or other project management tools that require referencing specific notes in commits. By reusing the same ID across multiple templates, you can maintain consistency and organization throughout your notes, making it easier to track progress and collaborate with others.

The Timesheet plugin is designed to help users create timesheets for tasks logged in daily notes, particularly for tasks tracked in systems like JIRA. By recognizing task identifiers such as 'FBI-1', it groups and summarizes the time spent on each issue, making it easy to log hours and report them. The plugin supports customizable task number patterns and allows users to define how the timesheet report is rendered using templates. It automatically compiles time logs and offers the option to include external links to JIRA tasks. With its flexible settings, it helps streamline time tracking and reporting for project management within Obsidian.

The Jira Issue Managing plugin integrates Jira functionality into Obsidian, enabling users to manage Jira issues directly from their notes. With this plugin, users can import Jira issue details into Markdown files, create new issues in Jira by specifying priorities and summaries, and update existing issues based on frontmatter metadata. It simplifies project management workflows by providing a seamless connection between Obsidian and Jira, complete with modal suggestions for selecting projects and issue types. The plugin requires authentication details, including username, password, and API URL, to interact with Jira effectively.