@softspark/jira-mcp 1.15.0 → 1.16.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/CHANGELOG.md +31 -0
  2. package/README.md +8 -8
  3. package/dist/cli.js +36 -36
  4. package/dist/index.js +25 -25
  5. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -7,6 +7,37 @@ Versioning follows [Semantic Versioning](https://semver.org/).
7
7
 
8
8
  ---
9
9
 
10
+ ## v1.16.0 -- Creator and reporter on every task read (2026-09-18)
11
+
12
+ `@softspark/confluence-mcp` has no behaviour change in this release; it is bumped
13
+ together with `@softspark/jira-mcp` per ADR-0002.
14
+
15
+ ### Added
16
+
17
+ - **`creator` and `reporter` in task reads.** `search_tasks`,
18
+ `get_task_details`, `sync_tasks` and `read_cached_tasks` now return who filed
19
+ an issue and who it is reported by. Until now the connector fetched `creator`
20
+ only for the `delete_task` ownership guard and never asked Jira for
21
+ `reporter`, so an agent asked "who raised this bug" had nothing to answer
22
+ from and went looking for a way around the server. Both fields hold the
23
+ email, or the display name when Atlassian privacy settings hide the email,
24
+ and `null` when Jira returns none. `reporter` is editable in Jira and can be
25
+ empty; `creator` never changes.
26
+ - The `search_tasks` and `get_task_details` tool descriptions name the fields a
27
+ result carries, so a client can tell what is available without a trial call.
28
+
29
+ ### Changed
30
+
31
+ - **Task cache rows carry `creator` and `reporter`.** The schema defaults both
32
+ to `null`, so a cache file written by an older version still loads and
33
+ `CACHE_VERSION` stays `1.0`. Rows cached before the upgrade read `null` until
34
+ the next `sync_tasks`.
35
+
36
+ ### Fixed
37
+
38
+ - `kb/reference/api.md` showed `get_task_details` answering in a plain-text
39
+ layout the tool never produced. The example is now the JSON it returns.
40
+
10
41
  ## v1.15.0 -- Tempo worklogs and reports (2026-09-17)
11
42
 
12
43
  `@softspark/confluence-mcp` has no behaviour change in this release; it is bumped
package/README.md CHANGED
@@ -4,17 +4,16 @@
4
4
 
5
5
  [![CI](https://github.com/softspark/jira-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/softspark/jira-mcp/actions/workflows/ci.yml)
6
6
  [![npm](https://img.shields.io/npm/v/@softspark/jira-mcp)](https://www.npmjs.com/package/@softspark/jira-mcp)
7
- [![version](https://img.shields.io/badge/version-1.15.0-blue)](CHANGELOG.md)
7
+ [![version](https://img.shields.io/badge/version-1.16.0-blue)](CHANGELOG.md)
8
8
  [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
9
9
 
10
10
  ---
11
11
 
12
- ## What's New in v1.15.0
12
+ ## What's New in v1.16.0
13
13
 
14
- - **Tempo worklogs and reports.** `search_tempo_worklogs` lists Tempo Timesheets entries in a date range with issue keys and user names resolved; `get_tempo_report` sums hours by project, user and/or task. Filters combine, so "this person's hours on this project last month" is one call.
15
- - Tempo REST API v4 answers in numeric ids only, so every result is joined against Jira. An issue the token cannot browse keeps its hours under `#<id>` instead of vanishing from a total.
16
- - `jira-mcp config set-tempo-token` stores the Tempo token next to the Jira credential, per site with `--url`. Nothing else needs it: without a token the two Tempo tools answer `TEMPO_NOT_CONFIGURED` and every other tool works as before.
17
- - Fixed: `config set-credentials` no longer drops a stored Tempo token when the Jira token is rotated.
14
+ - **`creator` and `reporter` on every task read.** `search_tasks`, `get_task_details`, `sync_tasks` and `read_cached_tasks` now say who filed an issue and who it is reported by. Before, neither field reached a response, so "who raised this bug" had no answer.
15
+ - Both hold the email, or the display name when Atlassian privacy settings hide the email, and `null` when Jira returns none. To filter by them, use JQL: `creator = "pm@example.com"` or `reporter = currentUser()`.
16
+ - An existing task cache keeps loading. Rows cached before the upgrade read `null` for both fields until the next `sync_tasks`.
18
17
  - Released together with `@softspark/confluence-mcp` under one version. See the [changelog](CHANGELOG.md).
19
18
 
20
19
  ## Table of Contents
@@ -207,10 +206,11 @@ Configuration is automatically loaded from `~/.softspark/jira-mcp/`. Run `jira-m
207
206
  If you use `@softspark/ai-toolkit`, register the Jira rules so that Claude Code automatically follows project conventions (language checks, sync-first workflow, time format, etc.):
208
207
 
209
208
  ```bash
210
- ai-toolkit rules add jira-mcp --path /path/to/jira-mcp/rules/jira-mcp.md
209
+ ai-toolkit add-rule https://raw.githubusercontent.com/softspark/jira-mcp/main/rules/jira-mcp.md
210
+ ai-toolkit update
211
211
  ```
212
212
 
213
- Or copy `rules/jira-mcp.md` to your ai-toolkit rules directory manually. The rules file covers:
213
+ The URL form is re-fetched on every `ai-toolkit update`, so the rules follow releases. A local path works too (`ai-toolkit add-rule /path/to/jira-mcp/rules/jira-mcp.md`) but stays frozen at that copy. The rules file covers:
214
214
  - **Language first** -- always check project language before writing comments/descriptions
215
215
  - **Sync before read** -- cache may be stale
216
216
  - **Status transitions** -- check valid transitions before changing status