Loading...
Product
Core Features
Top Extensions
Company
Subscribe to our newsletter.
Get product updates and news in your inbox. No spam.
Create, access and modify issues and sprints.
The Jira extension supports OAuth authentication by default. But if you want, you can log in with an API token instead. To do so, you must:
⌘ + K and scroll down to Configure Extension. Enter your email, API token, and Jira site URL (without https://) on the right. Note that all three must be provided to use API tokens.You can change the default Git branch name in preferences; the following keys are available:
Create and assign new issues.
View your open issues with optional Active Sprint, All Sprints, and Backlog sections.
View and modify issues that were reported by you.
View and modify issues that you are watching.
View and modify issues of active sprints.
View and modify issues of your saved filters.
View and modify issues that have recently been updated.
Search issues globally in all projects.
Open an issue by its key from the clipboard.
atlassian-team), so a team can now be selected and set on new issuesatlassian-team) and the Advanced Roadmaps Team field (rm-teams-custom-field-team), both sent as a plain-string Team ID (an { id } object is silently dropped)npm test via Node's built-in node:test runner)Unexpected token '<' when Jira returns an HTML login, redirect, or SSO page instead of JSON (#23569, #23474, #23413, #23367).Open Issues checkboxes to choose which sections to show: Active Sprint, All Sprints, and Backlog.All Sprints view in Open Issues to split issues by sprint name instead of showing a single combined section.Open Issues behavior as the implicit default when no section checkbox is enabled.Open Issues in Active Sprint command since equivalent behavior is now configurable in Open Issues.invalid_grant failures, prompting users to reconnect Jira in extension preferences.Open Issues preference descriptions for clearer in-app configuration guidance./browse/KEY issue link.created >= -30d clause in the Search Issues command when no project is selected to prevent Jira’s “Unbounded JQL queries are not allowed” error./search endpoint with the new enhanced search-based API (POST /search/jql).searchResults / values.src/api/issues.ts and related hooks to prevent runtime errors after Atlassian CHANGE-2046.[issue.key - issue.fields.summary]Search Issues command. If a project is selected, you can simply input the ticket number in the search query for faster results.Missing required property "title" for Unknown).Show Details would show up on the issue's detail view.Statuses in Jira may not have categories. Problem is, these categories are used as a section title in various commands such as Open Issues causing the error:
Error: Rendering failed:
Missing required component property "title"
This should be fixed now!
Create Issue command