This is a workflow for Alfred 2 (or Alfred 3) that can be used to interact with JIRA.
npm run build
.) but the last character in the summary must be a period in order to submit the new issue. This is a precaution used to prevent premature submission of new issues.
cmd + enterwhen submitting the issue to open the newly created issue in the browser.
alfred-jirahas two bookmarks for issues assigned to you and issues that you are watching.
jirafollowed by the search string will search all of your bookmark results
enterwill POST the comment to the issue.
jirastarts the workflow and allows the user to navigate through the menus/search issues
jiraopen– Short cut for opening an issue in the browser. The issue key must be given as a parameter:
jiraclear– Clears the progress timer for an issue without logging the time to JIRA.
After installing the workflow and logging in, the workflow will default to include all projects and statuses available in your JIRA instance. It is recommended that you open the settings pane and configuring the workflow to show only the projects and issue statuses that you are interested in. For example: disabling
Closed issue statuses.
This can be easily done by selecting
Edit Settings from the
Settings menu and clicking the buttons associated with the statuses you wish to disable/enable.
When logging time to issues, you may wish to set a minimum amount of time to log. A minimum can be set by adding the desired amount of time to the "minimum time to log" field of the settings pane. The format for time is the same as in JIRA:
.5 h and
30m both log a minimum of
30 minutes to issues you work on.
It is possible to define an increment with which to round your log time by defining "Round time to the nearest increment" in the settings pane. Doing so will round your time spent on an issue to the nearest
increment defined. For example: with
15 mins increments,
1 hour 51 minutes spent on an issue would be logged as
2 hours. Note that the format of the value is the same as described in the Minimum Log Time section.
By default, the workflow is set up to perform a basic search. Meaning, from the search option, Alfred will return a list of issues that contain the string(s) you typed in their summary, description, or comment fields. If you would prefer more control over the search, you can enable JQL searching by ticking the "Advanced Search (JQL)" under the Settings header of the settings pane.
By default, all items associated with a specific issue will be returned when viewing an issue's details. You can specify which items are returned so that the information that is pertinent to you is easily accessible. Enable/disable menu items from the settings pane.
You can download the image resources associated with the workflow's enabled projects, users, and priority levels via the buttons at the bottom of the settings pane under the Optional header.
In order to authenticate against the JIRA API, your username/password will be required. They will be saved in Keychain Access under the name
alfred-jira. Additionally, a configuration file will be created at
~/.alfred-jira. Both can be removed by selecting Logout from the settings pane.
For better performance, some information is persisted in
You also have the ability to enable background cacheing by selecting "Refresh workflow cache in the background" in the settings pane. Once you specify a time interval and save the settings, the app will create a LaunchAgent file (
$HOME/Library/LaunchAgents/com.alfred-jira.helper.plist) that will keep your issues synced with the server so that you don't experience any lag when navigating your bookmark queries. The LaunchAgent only runs when it can connect to your Jira instance and is disabled when your credentials are invalid to prevent an accidental account lockout.