Are you tired of copying Jira links, only to not remember which Jira is it? What about getting updates without clicking on each link? Or querying blocks within Logseq based on ticket status?
Bring your Jira issue status and summaries into Logseq with Logseq-Jira. Include important fields like Priority, Status, Assignee and Reporter as block properties to then query within Logseq as needed.
Check out the discussion on Logseq Forums by clicking here
- Use the slash command "Update Jira Issue" to replace issue keys (PM-100, ISS-12143, etc.) or Jira issue links like subdomain.atlassian.net/browse/PM-100 with
[<issueKey>|<issueSummary>](https://orgname.atlassian.net/browse/<issueKey>)formats. - Use optional block properties to keep the text as in, but add key issue fields as block properties.
- NEW Supports two Jira Cloud instances. Keep your work JIRA separate from your personal JIRA.
- Earlier issue details are not automatically updated. (Need to check performance impact).
- Supports Jira Cloud only.
- Refresh summary on rerun on existing links.
- Add more fields to help with context of the tickets
- Support for multiple organizations.
- Auto refresh/update all links when page is loaded.
- Auto refresh all Jira links across vault (need to verify performance impact on doing this).
- Create your own Link description format with Jira variables ( '{issueKey} - {status} - {summary}' )
The plugin is available to download directly from Logseq's Plugins marketplace. Alternatively, you can download the latest release from Releases published on Github.
- Git clone the repository to your local system. Or download and extract to a known path.
npm install && npm run buildin terminal to install dependencies and generate distribution folder.- Enable Developer mode in Logseq by going to Settings -> Advanced -> Turn on Developer Mode.
Load unpacked pluginin Logseq Desktop client and select the folder for the plugin on your disk.- For updates, git pull the main branch and 'Reload Package' under Plugins > Logseq Jira.
- Update version in package.json
- Add all updates to master branch
- Tag the latest commit with new version.