v2.0.0

Jira for Alfred v2 is the next major release of the workflow, with extensive architectural changes and welcome fixes. The end-user API is still the same—a single jira keyword within Alfred. The most significant change is that the search algorithms have been rewritten from the ground up to be JQL-based, which exposes new capabilities and makes the search experience more predictable.

No new changes since v2.0.0-beta.1

New Features

Access to all issues, not just those previously-viewed

This new JQL-based architecture solves a longstanding annoyance where the workflow could only find issues that your Jira user has previously viewed; now, the workflow can find any issue you have access to, regardless of whether or not you've viewed it. For convenience, however, the workflow still lists previously-viewed issues above issues you haven't viewed at all.

Restricting searches to specific projects

You can now 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.