Ticketpane: known limits

What Ticketpane does not do yet, and what happens when Jira, Polar, or your network misbehave. Everything on this page was tried against a real Jira Cloud site and real Polar on 2026-09-10. If something here bites you, email support and say which line.

Signing in

• A mistyped site name says "There is no Jira Cloud site at …". Atlassian answers for every something.atlassian.net, even ones that do not exist, so Ticketpane cannot tell a typo from a missing site any other way. Check the spelling and try again.
• A mistyped domain (for example atlasian.net) says "That address does not exist". This is a spelling problem, not a network problem.
• Pasting your Atlassian password instead of an API token fails with a 401. Jira Cloud only accepts API tokens. Create one at id.atlassian.com under Security, then API tokens.
• A site your account is not a member of also fails with a 401. Jira does not distinguish "wrong token" from "not a member". If the token works on another site, ask that site's admin to add you.
• Email case does not matter. MIKE@EXAMPLE.COM signs in the same as mike@example.com.
• Custom Jira Cloud domains are supported, with a warning. Any address that is not something.atlassian.net shows a confirmation naming the server before your token is sent to it.
• Jira Server and Data Center are not supported. Ticketpane uses Jira Cloud's REST API and Atlassian's cloud gateway only.
• No OS keyring, no sign-in. On Linux without a keyring (for example a bare container, or a locked keychain), Ticketpane loads on the Free tier and sign-in reports the keyring error instead of storing the token. It never writes the token to disk in plain text.

Reading issues

• One page of issues at a time, up to 100. The sidebar shows a single page of the most recently updated issues that match: up to 100, and sometimes fewer, because Jira's search pages by token and can hand back a short page. When Jira says there is more behind that page, the last row in the tree says so — naming how many issues you are actually looking at, on the rare empty page just that there are more — and opens the same query in Jira, which has the whole list. There is no "load more" inside the editor yet — narrow the filter if you want the older ones in the sidebar.
• Filters need a search condition. A saved filter that is only ORDER BY created DESC is rejected by Jira with "Unbounded JQL queries are not allowed". Add something like project = ABC in front.
• A saved filter that matches 1,000 issues shows one page too. The same single page as above, whatever the filter, with the same "open in Jira for the rest" row underneath it.
• Bad JQL shows Jira's own error. The message names the character position, for example "Expecting either 'OR' or 'AND' but got '='. (line 1, character 17)".
• The 50 newest comments only. The panel header names the real total — "Comments (50 newest of 312)" — and the older ones are in Jira, one click away via "Open in browser".
• 100 projects in the Create Issue picker. Sites with more projects see the 100 with the most recent activity.
• Attachments open in the browser. Ticketpane lists the filenames and links to Jira. It cannot show or upload attachments in the editor.
• The sprint chip is best-effort. If the site's sprint field cannot be found, the chip is simply missing. Nothing else is affected.
• Rich content is rendered in a plain style. Tables, code, panels, expands, decisions, task lists, mentions, emoji, dates and status lozenges all render. Layout columns render one after another instead of side by side. Embedded media (images, videos) shows as a placeholder. Anything Ticketpane does not recognise shows its text. Scripts and javascript: links in issue text are never executed.
• Long issues are fine. A 10,000-character description and a 30,000-character comment were tested and render correctly.

Writing to Jira

• Comments and descriptions are capped at 32,767 characters. That is Jira's limit for a text field. Ticketpane stops you before sending and tells you the count, rather than letting Jira reject it.
• Summaries are capped at 255 characters. Same reason.
• A blank or whitespace-only comment is refused with "Write something first". Jira would otherwise save an empty comment.
• Creating an issue sends project, type, summary, description, and you as the assignee so it appears in My Issues right away. A project that will not let you be assigned gets the issue unassigned; the Open button on the "Created" toast still reaches it. If the type requires other fields (a component, a custom field), Ticketpane names them and opens Jira's own New Issue form with your summary and description filled in.
• Which transitions you see depends on the workflow. Ticketpane lists exactly what Jira offers for that issue in its current status. A "Done" issue can usually be reopened because Jira's default workflow allows it.
• No editing of summaries, descriptions, or comments, no deleting, no worklogs, no assigning to someone else. Transition and comment are the only writes besides creating an issue.
• Create Branch needs an open Git repository. If the window has none, or Git refuses (branch already exists, invalid name), Ticketpane shows Git's message instead of creating the branch.

Editors

• VS Code Restricted Mode blocks "Branch from issue" until the folder is trusted. In a folder you have not trusted yet (Workspace Trust), Ticketpane cannot run Git, so the command reports that instead of creating the branch. Click Manage on the Restricted Mode banner (or the shield in the status bar) and choose Trust; the command works straight away.
• Cursor's Agents window has no Command Palette, so no Ticketpane commands. Cursor opens in its Agents layout by default; the sidebar view and the Command Palette live in an IDE window. Open one with Cursor → New Window (or cursor -n <folder> from a terminal) and run Ticketpane there.
• Cursor installs from its own mirror of Open VSX, which can lag. A new Ticketpane version shows on open-vsx.org first and in Cursor's Extensions view some hours later. Windsurf and VSCodium read Open VSX directly.

Network and slow Jira

• Every Jira request gives up after 30 seconds and says Jira may be down or very slow. Try again shortly.
• A wrong VPN or proxy shows a readable reason. Connection refused, connection timed out, and certificate problems are each named in the message.
• No offline cache. Without a connection the sidebar cannot load issues. Issues you already opened stay visible until you refresh.

Licenses and the Pro trial

• The 14-day trial starts the first time Ticketpane runs. It cannot be restarted by signing out or by uninstalling and reinstalling: the editor keeps the trial's start date (uninstall and reinstall checked in desktop VS Code 1.138, September 2026). Each editor, and each VS Code profile, has its own extension storage, so installing Ticketpane in a second editor (VS Code, Cursor, Windsurf) or in a new profile starts its own trial there.
• A key pasted with spaces, line breaks, or in lowercase still activates. Ticketpane cleans it up before sending.
• A key from another Polar store, a mistyped key, or a made-up key shows "Polar does not recognise that license key". Polar answers the same way for all three.
• A key can be active on 3 machines. The fourth activation is refused with "activation limit already reached". Deactivate a machine in your Polar customer portal (Purchases, then Ticketpane Pro) and try again.
• Polar throttles activation attempts. A burst of tries in one minute can be refused with "Polar is limiting activation attempts right now". Wait a minute and try once.
• Activation gives up after 15 seconds. A captive Wi-Fi portal or proxy that answers with a web page instead of Polar's reply is treated as "could not reach Polar", and nothing is stored.
• A revoked or refunded key drops to Free at the next check, which can be up to 24 hours later. Ticketpane re-checks a key at most once a day.
• Offline, Pro keeps working for 7 days from the last successful check. After that it falls back to Free until Polar can be reached again. A Polar outage never locks out a paying customer inside that window.
• The active site is shared across editor windows. Switching site in one VS Code window switches it everywhere.
• The Free tier connects one Jira site. Adding a second offers to replace the first, or to buy Pro.

Not built yet

Pagination past 100 issues, editing issue text, attachment upload, worklogs, assigning to others, an offline issue cache, side-by-side layout columns, and translations.