Discussion Brief Cards
Read GitHub discussions beside project notes.
Enterprise Issue Cards keeps private issue details beside your notes
Read Enterprise issues as text cards with local copies.
MIT · no telemetry · core features free
- version
- 1.1.0
- downloads
- 21
- review
- Passed
- health
- Excellent
- license
- MIT
- listed for
- Desktop, Mobile
- obsidian
- 1.13.4 or later
Mac desktop checks use local issue responses; no live Enterprise Server or physical mobile device was tested.
Directory facts fetched from community.obsidian.md/users/theluckystrike.
About Enterprise Issue Cards
You keep project notes for work tracked on a GitHub Enterprise Server and need issue details beside the plan.
Put an Enterprise issue URL in a ticket block to show its title, state, labels, author and body. The card keeps a local copy with a fetch time. A previously fetched issue remains readable when the server is offline.
Set your server's root HTTPS host and save a read token in Obsidian secret storage. The free version supports one primary server.
Play demoFree features
Ticket cards in notes
The issue fields appear as plain text, with body line breaks preserved. Image syntax and HTML stay text instead of creating images or scripts. The original ticket block stays in your note.
One server and a secret token
Set a root HTTPS server host and save its read token in Obsidian secret storage. HTTP and base paths are rejected. The plugin checks an issue URL against an authorized host before requesting it.
Cache and manual refresh
A cached card doesn't fetch again when it renders. Concurrent reads of one issue share a request. Select Refresh to update the local copy and open cards for that issue.
Access and network messages
Access, rate-limit and network errors keep cached fields and show a message; a 404 removes that issue from the cache. Rate limits pause automatic reads for at least an hour in the current session. Manual retry remains available.
One primary server, cached cards and manual refresh are free; additional server profiles and saved-list tools need Pro.
Pro features
Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.
Named server profiles Pro
Add named HTTPS server profiles with separate tokens by host. Removing a profile stops its use for cards but leaves its secret in Obsidian storage. Additional hosts stop working when Pro turns off.
Scheduled saved-list refresh Pro
Refresh a saved list of up to 50 distinct issue URLs while Obsidian is open. Set 10 to 1440 minutes between operations, or 0 to stop scheduling. Reads run in sequence with a one-second pause.
Local project list Pro
Open the project list to read cached fields and fetch times for saved URLs. Opening it sends no issue request. Tickets without a cached copy show a message.
Set up Enterprise Issue Cards
needs
- Obsidian 1.13.4 or later
- A GitHub Enterprise Server at a root HTTPS host, with an account that can read the required issues.
- A read token approved for use with those private issues.
steps
Install Enterprise Issue Cards from Community plugins and enable it.
In its settings, enter the root HTTPS server host without an API path.
Paste an approved read token and select Save token.
Write a fenced code block with the language ticket and an issue URL on its first nonempty line.
Open Reading view to fetch an uncached card, or select Refresh to update an existing copy.
If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.
Known limits of Enterprise Issue Cards
- Only root HTTPS GitHub Enterprise Server hosts are supported; HTTP hosts and base paths are rejected.
- Public GitHub issue fetching, pull-request merge status and Markdown body rendering are outside this build.
- Cards render plain text, so issue image syntax and HTML do not create images or scripts.
- Cached private issue titles and bodies live in plugin data, which vault sync or backups can copy.
- A 404 response removes the issue from the cache, even when an older copy was available.
- A rate limit pauses automatic reads for at least an hour in the current app session; manual retry remains available.
- Removing a named server profile leaves its token in Obsidian secret storage.
- Scheduled refresh runs only while Obsidian is open and reads at most 50 distinct saved issue URLs.
- The saved list keeps its first 50 lines before removing duplicate URLs, so blank or repeated lines can reduce the issue count.
- Issue reads send the configured server token and issue identifiers before Sponsors sign-in when an uncached card needs them.
- No live Enterprise Server, private certificate authority, redirect behavior, Linux runtime, mobile device or real GitHub payment was tested.
Need a change for your team? I build custom Obsidian plugins and features.
Questions about Enterprise Issue Cards
Can I use this with public GitHub issues?
Public GitHub issue fetching is outside this build. The plugin targets the issue REST endpoint on your configured GitHub Enterprise Server.
Where does the private issue text go?
Cached titles and bodies live in the plugin's data.json. A backup or vault sync can copy that file. Server tokens use Obsidian secret storage instead of saved plugin settings.
Does the card render Markdown or edit issues?
The body stays plain text, including image syntax and HTML. The plugin reads issues and doesn't edit them or change your note text.
Has it been checked against a live Enterprise Server?
No live Enterprise Server was available for the reported tests. Unit and app checks use local responses, fake tokens and cached sample issues.
What happens when the server returns 404?
The issue's cached copy is removed. The card shows a missing-issue message, so check the URL and whether your token can read the private issue.
Network use
Uncached cards, manual Refresh and Pro saved-list refreshes send the server token, owner, repository and issue number to your configured HTTPS Enterprise hosts. Sponsors sign-in sends a client ID, scope and device code to github.com; sponsorship queries send your token to api.github.com. GitHub checks follow sign-in, Refresh or cache expiry; issue reads can precede sign-in, without note names, local paths or surrounding text.
Questions or ideas?
Tell me what is broken in Enterprise Issue Cards, or what it should do next.
Enterprise Issue Cards 1.1.0, MIT license
MIT · no telemetry · core features free
Related plugins
Context Trees
Show parent headings and lists in search results.