ticketlens 0.19.0 → 0.20.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticketlens",
-  "version": "0.19.0",
+  "version": "0.20.1",
   "description": "Jira CLI for developers — fetch ticket context, triage your queue, and stop tab-switching. Zero dependencies, all local.",
   "type": "module",
   "bin": {

package/skills/jtb/SKILL.md

@@ -1,4 +1,4 @@
-<!-- jtb-skill-version: 0.19.0 -->
+<!-- jtb-skill-version: 0.20.1 -->
 ---
 name: jtb
 description: Fetch a Jira ticket's full context (description, comments, linked issues, code references) and assemble a structured TicketBrief for implementation planning. Use when user types /jtb, mentions a Jira ticket key, or wants to plan work from a Jira ticket.
@@ -345,6 +345,10 @@ When `--push` is run by a Pro-licensed user, the local compliance ledger (writte
 
 Non-Pro users push with `compliance_status: unknown` — no data is lost, and the analytics page simply shows no compliance data for those snapshots.
 
+### triage --push priority/label fields (Team)
+
+`--push` now includes each ticket's `priority` and `labels` in the payload (previously omitted). This feeds two Console features under `/console/admin/rules`: real-value suggestions for the Priority/Label fields when building custom attention rules (previously only Status/Key prefix had them), and the `notify`/`schedule` custom-rule actions, which match on priority/label server-side. No new flag — this is automatic on every `--push`.
+
 ### --plain / --styled
 
 Control output formatting:

package/skills/jtb/scripts/lib/attention-scorer.mjs

@@ -75,6 +75,23 @@ export function findLastEffectiveComment(comments, currentUser) {
   return { comment: null, fromCurrentUser: false };
 }
 
+/**
+ * Test whether a ticket satisfies a rule's match conditions.
+ * Ported 1:1 to PHP as CustomRuleMatcher::matches() — keep both in sync,
+ * parity enforced by fixtures/custom-rule-match-cases.json.
+ */
+export function matchesRuleConditions(ticket, match) {
+  const { priority, label, status, keyPrefix } = match;
+  if (priority !== undefined && ticket.priority !== priority) return false;
+  if (status !== undefined && ticket.status !== status) return false;
+  if (label !== undefined) {
+    const labels = Array.isArray(ticket.labels) ? ticket.labels : [];
+    if (!labels.includes(label)) return false;
+  }
+  if (keyPrefix !== undefined && !String(ticket.key).startsWith(keyPrefix)) return false;
+  return true;
+}
+
 /**
  * Apply a single custom rule against a ticket.
  * Returns 'force-urgent' | 'ignore' | null.
@@ -83,17 +100,7 @@ export function findLastEffectiveComment(comments, currentUser) {
 function applyCustomRule(ticket, rule) {
   if (!rule || typeof rule.match !== 'object' || !rule.match) return null;
   if (rule.action !== 'force-urgent' && rule.action !== 'ignore') return null;
-
-  const { priority, label, status, keyPrefix } = rule.match;
-  if (priority !== undefined && ticket.priority !== priority) return null;
-  if (status !== undefined && ticket.status !== status) return null;
-  if (label !== undefined) {
-    const labels = Array.isArray(ticket.labels) ? ticket.labels : [];
-    if (!labels.includes(label)) return null;
-  }
-  if (keyPrefix !== undefined && !String(ticket.key).startsWith(keyPrefix)) return null;
-
-  return rule.action;
+  return matchesRuleConditions(ticket, rule.match) ? rule.action : null;
 }
 
 export function scoreAttention(ticket, currentUser, opts = {}) {

package/skills/jtb/scripts/lib/ticket-payload.mjs

@@ -9,6 +9,8 @@ export function buildTicketPayload(scored, rawMap, baseUrl) {
     summary: scored.summary ?? null,
     status: scored.status ?? null,
     assignee: raw?.assignee ?? null,
+    priority: raw?.priority ?? null,
+    labels: Array.isArray(raw?.labels) ? raw.labels : [],
     attention_score: null,
     flags: scored.urgency === 'clear' ? [] : [scored.urgency],
     // last_comment_at feeds server-side response-time metrics (F19c).