https://github.com/caleb531/jira-for-alfred
An Alfred workflow for listing out Jira tickets, among other things
Science Score: 26.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (16.4%) to scientific vocabulary
Repository
An Alfred workflow for listing out Jira tickets, among other things
Basic Info
- Host: GitHub
- Owner: caleb531
- License: mit
- Language: Python
- Default Branch: main
- Size: 1.35 MB
Statistics
- Stars: 7
- Watchers: 2
- Forks: 2
- Open Issues: 2
- Releases: 16
Metadata Files
README.md
Jira for Alfred
Copyright 2023-2025 Caleb Evans
Released under the MIT license
This Alfred workflow allows you to quickly search for and open any Jira ticket you have access to.
Installation
To download the workflow, simply click one of the download links below. Please note that only the Alfred 5 version has all the latest features.
Download Jira for Alfred (Alfred 5)
Command Line Tools
If you are installing the workflow for the first time, you may be prompted to install Apple's Command Line Tools. These developer tools are required for the workflow to function, and fortunately, they have a much smaller size footprint than full-blown Xcode.

Usage
Configuration
In order to use the workflow, you must provide three bits of info:
- The base URL of the Atlassian team (e.g.
https://yourcompany.atlassian.net); any trailing slashes are ignored - The username of your Jira account
- An access token for your Jira account (Atlassian account settings > Security tab > API tokens)
You must input these configuration parameters when you first install the workflow, and you can change them at any time.
Searching for issues
The main usage of the workflow is through the jira keyword. If you don't provide a query, your most recent issues are shown.
You can look up a particular issue by summary or key. When an issue is selected, you can perform any of the following actions:
- Press Enter open the issue page in your browser (the default behavior)
- Press Command-Enter to copy the key/ID of the issue (e.g. "ABC-123")
- Press Option-Enter to copy the issue's URL
- Press Shift-Enter to copy the issue summary (e.g. "Fix the thing")

Restricting searches to specific projects
You can optionally restrict your search to one or more projects using the Restrict to Projects configuration option within the workflow's settings. This provides another way to cut down on the number of issues you might be presented with.
To use it, enter a comma-separated list of project keys (e.g. if you want tickets like ABC-123 and DEF-234, then enter "ABC, DEF" into the field). If you leave the field blank, then you get the default behavior of searching across all projects your Jira account has access to.
Viewing recently-worked-on issues
If you do not pass a search query to the jira keyword, the workflow will
automatically display your recently-worked-on issues.
On-premise users
If you are an on-premise user using the 9.12.x LTS datacenter/server edition of Jira, then enable the Use Jira 9.12.x LTS configuration option within the workflow's settings. This should fix any errors with loading issues.
Quicker issue lookup for single-project setups
If you only have a single project for which you wish to look up issues, then
specify the project key in the Prepend Number-Only Queries with Project Key
configuration option within the workflow's settings. This will allow you to
specify number-only queries (e.g. jira 123), and the project key will
automatically be prepended (with a dash) to the number you specify.
For example, if you specify PROJ as your project key to prepend, then type
jira 123 into Alfred, the issue PROJ-123 will be retrieved.
Disclaimer
This project is not affiliated with Atlassian, and the Jira icons used in this project are property of Atlassian.
Owner
- Name: Caleb Evans
- Login: caleb531
- Kind: user
- Location: Carlsbad, CA
- Website: https://calebevans.me/
- Twitter: caleb531
- Repositories: 76
- Profile: https://github.com/caleb531
Hi, I'm Caleb, a web developer who lives for Christ by building enjoyable apps and useful tools. I hope you are blessed by what I've made!
GitHub Events
Total
- Create event: 8
- Issues event: 4
- Release event: 5
- Watch event: 3
- Delete event: 3
- Issue comment event: 23
- Push event: 41
- Pull request review comment event: 3
- Pull request review event: 9
- Pull request event: 6
- Fork event: 2
Last Year
- Create event: 8
- Issues event: 4
- Release event: 5
- Watch event: 3
- Delete event: 3
- Issue comment event: 23
- Push event: 41
- Pull request review comment event: 3
- Pull request review event: 9
- Pull request event: 6
- Fork event: 2
Issues and Pull Requests
Last synced: 10 months ago
All Time
- Total issues: 2
- Total pull requests: 4
- Average time to close issues: N/A
- Average time to close pull requests: 15 days
- Total issue authors: 2
- Total pull request authors: 2
- Average comments per issue: 0.0
- Average comments per pull request: 1.0
- Merged pull requests: 2
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 2
- Pull requests: 4
- Average time to close issues: N/A
- Average time to close pull requests: 15 days
- Issue authors: 2
- Pull request authors: 2
- Average comments per issue: 0.0
- Average comments per pull request: 1.0
- Merged pull requests: 2
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- evilsquirr3l (1)
- NoxoN1602 (1)
- jangelsb (1)
Pull Request Authors
- jangelsb (2)
- mcowger (1)