1What FoxPlug reads from Jira
These are the exact things it reads, and nothing else.
| What | The details it takes |
|---|---|
| Issues that reached Done | issues whose status category is Done and that were resolved in the look-back window (at most the last 30 days), newest resolved first, up to 50 |
| Issue key and summary | the issue key (e.g. ACME-12) and its summary, summary cut to 160 characters |
| Issue type | the issue type name, used with labels to decide feature, bug or other |
| Labels | the issue's labels, used with the type to decide feature, bug or other |
| Resolution date | when the issue was resolved; becomes the moment's time |
| Project | the project name (or key), cut to 80 characters, shown in brackets |
2Moments it finds, and what each becomes
A moment is one thing that happened in Jira worth a second look. Each one is scored, then it becomes a post, a changelog entry, a thing to fix or an idea to email, or it is skipped.
A feature-type issue reaches Done
The moment is titled like this: Shipped: Add saved filters
You resolve the Story 'Add saved filters' in the project Acme Web. FoxPlug writes 'Shipped: Add saved filters' with 'A feature closed in Jira (Acme Web): Add saved filters.' and the brain can offer it as a say card.
A bug-type issue reaches Done
The moment is titled like this: Fixed: Login page crashes on Safari
You resolve a Bug called 'Login page crashes on Safari'. FoxPlug writes 'Fixed: Login page crashes on Safari' with the line 'A bug fix (changelog line, not a post).' It is kept for the changelog and is not a post; a week of only bug fixes adds to the Skip line.
Any other issue type reaches Done
The moment is titled like this: Closed: Rotate API credentials
A Task called 'Rotate API credentials' is resolved. FoxPlug writes 'Closed: Rotate API credentials' and scores it like any other update.
3How the brain uses it
The rules below are the ones that apply to Jira. The same rules, with worked examples, are on the brain page.
- A closed feature becomes a say line, 'Shipped: Dark mode'. How the brain decides
- A closed bug becomes 'Fixed:...' and is kept for the changelog. It is not a post, and a bug-only week adds to the Skip line. How the brain decides
- Other closed work shows as 'Closed:...' and is scored like any update. How the brain decides
- What counts as a bug or a feature is the issue type (Jira) or the labels and tags (GitHub, ClickUp). A bug label wins over a feature label. How the brain decides
4Set up Jira in a few steps
Access: your Atlassian email plus an API token, pasted together as email:token, and your Jira Cloud site name. What to give it: your email + an API token (FoxPlug only reads).
- In Atlassian, open Security and then API tokens and press Create API token.
- Name it FoxPlug and pick an expiry. Copy the token now; Atlassian shows it only once.
- In the token box paste your Atlassian email, then a colon, then the token, with no spaces: you@example.com:the-token.
- In the Site box, type your Jira address, for example acme.atlassian.net.
- Press Check for what's new.
5Limits worth knowing
Where it stops, so nothing surprises you.
- Reads at most 50 resolved issues per read and looks back no further than 30 days, or since your last read if that is more recent.
- Jira Cloud only: the site must look like yourname.atlassian.net; a name without the domain is accepted and completed.
- A bug word (bug, defect, regression, hotfix, crash, incident, fix) in the type or a label wins over a feature word (feature, enhancement, improvement, story, epic, request, idea).
- The token is pasted as email, a colon, then the token; without the colon the read stops with an error.
- On the first read after connecting, only the single newest closed issue becomes a moment.
6What it never reads
Read only means read only, and the list below is what the code leaves alone.
- Reporter, assignee and comments
- Sprints and releases
- Issues that are not Done
- Anything it could write: the only call is a search
7How Jira differs from the tools next to it
Jira versus ClickUp, Asana, Trello and Linear: Jira (Atlassian email plus API token, Jira Cloud only) reads issues that reached the Done status category in a window, with type and labels, and sorts them into feature, bug or other. ClickUp (personal token) does the same sort from tags. Linear reads the 25 latest completed issues and does not sort. Asana reads tasks assigned to the token's owner plus new projects. Trello reads cards that sit in lists named like Done.
8Questions
Does FoxPlug read who reported or is assigned to my Jira issues, or the comments?
No. It reads the key, summary, type, labels, project and when the issue was resolved. Reporter, assignee and comments are not read.
Does it work with Jira Server or Data Center?
The code accepts only Jira Cloud addresses of the form yourname.atlassian.net, so no.
How does FoxPlug tell a feature from a bug?
From the issue type name and the labels. A bug word wins over a feature word. Anything else is 'Closed'.
Has the Jira connection been tested against a real account?
No. It is marked code-path-only: the code path exists and its offline checks pass, but no real Jira site of ours has exercised it.
FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.