Unified Ticket Fetcher Skill
Stateless atomic operation to securely query multiple project management and enterprise ticketing platforms (Jira, Plane, ServiceNow), aggregate assigned work items, resolve credentials gracefully, and produce a single normalized task schema.
Prerequisites
unified-task-tracker — for orchestrating multi-provider authentication and issuing high-fidelity API requests to ticketing backends.
Steps
Step 1: poll_assigned_tickets
Identify and query active ticketing endpoints for the current user session:
- Locate active credentials and connection properties for:
- Jira: Resolve URL, username, and API token.
- Plane: Resolve workspace name, project IDs, and API key.
- ServiceNow: Resolve instance URL, client ID, and credential pairs.
- Execute parallel or sequential queries to each active ticketing platform:
- Call Jira endpoint (e.g., query
assignee = currentUser() AND statusCategory != Done).
- Call Plane endpoint (e.g., retrieve active issues assigned to user profile identifier).
- Call ServiceNow incident tracker (e.g., retrieve incidents where
assigned_to matches user ID and state is not resolved/closed).
- Output parameters:
raw_payloads: Dictionary mapping provider name (jira, plane, servicenow) to lists of raw ticket metadata.
Step 2: aggregate_ticket_payloads [depends_on: poll_assigned_tickets]
Collate raw records, manage connection failures, and extract core ticket attributes:
- Handle execution faults:
- If a specific provider API request fails (e.g., due to timeout or bad credentials), capture the exception, register a warning diagnostic, and continue processing other available backends (graceful degradation).
- Consolidate raw ticket listings:
- Merge the raw JSON arrays into a single in-memory collection.
- Apply global filter logic to remove completed, archived, or resolved issues.
- Output parameters:
aggregated_list: Consolidated list of active raw ticket metadata objects.
failed_providers: List of providers that failed to respond.
Step 3: normalize_tasks [depends_on: aggregate_ticket_payloads]
Transform heterogeneous ticket schemas into a single, standardized, unified task list:
- Standardize fields into the target schema:
id: Normalized ticket identifier string (e.g. JIRA-101, PLANE-402, SN-INC00123).
source: Provider identifier ("jira", "plane", or "servicenow").
title: Short title or summary string.
description: Main description body, stripped of platform-specific HTML/formatting where appropriate.
status: Normalized workflow state ("TODO", "IN_PROGRESS", "BLOCKED").
priority: Standardized severity level ("LOW", "MEDIUM", "HIGH", "CRITICAL").
due_date: ISO-8601 due date string (null if unspecified).
created_date: ISO-8601 creation timestamp.
- Sort and deduplicate:
- Remove duplicate records if any exist.
- Sort the task collection by priority descending, then by created_date ascending.
- Output parameters:
status: "SUCCESS" or "FAILED"
normalized_tasks: List of standard task objects containing all normalized keys.
task_count: Total number of active tickets retrieved.
1---2name: unified-ticket-fetcher-23skill_type: skill4description: >5 Unified Ticket Fetcher atomic skill. Connects to Jira, Plane, and ServiceNow,6 aggregates assigned tickets, and outputs standardized tasks.7domain: ops8license: MIT9tags: [tickets, jira, plane, servicenow, management]10metadata:11 source: https://skillmd.com/skills/knuckles-team/unified-ticket-fetcher-212 version: '1.6.0'13 author: Genius14requires:15 - unified-task-tracker16---1718# Unified Ticket Fetcher Skill1920Stateless atomic operation to securely query multiple project management and enterprise ticketing platforms (Jira, Plane, ServiceNow), aggregate assigned work items, resolve credentials gracefully, and produce a single normalized task schema.2122## Prerequisites2324- `unified-task-tracker` — for orchestrating multi-provider authentication and issuing high-fidelity API requests to ticketing backends.2526## Steps2728### Step 1: poll_assigned_tickets29Identify and query active ticketing endpoints for the current user session:30- Locate active credentials and connection properties for:31 - **Jira**: Resolve URL, username, and API token.32 - **Plane**: Resolve workspace name, project IDs, and API key.33 - **ServiceNow**: Resolve instance URL, client ID, and credential pairs.34- Execute parallel or sequential queries to each active ticketing platform:35 - Call Jira endpoint (e.g., query `assignee = currentUser() AND statusCategory != Done`).36 - Call Plane endpoint (e.g., retrieve active issues assigned to user profile identifier).37 - Call ServiceNow incident tracker (e.g., retrieve incidents where `assigned_to` matches user ID and state is not resolved/closed).38- Output parameters:39 - `raw_payloads`: Dictionary mapping provider name (`jira`, `plane`, `servicenow`) to lists of raw ticket metadata.4041### Step 2: aggregate_ticket_payloads [depends_on: poll_assigned_tickets]42Collate raw records, manage connection failures, and extract core ticket attributes:43- Handle execution faults:44 - If a specific provider API request fails (e.g., due to timeout or bad credentials), capture the exception, register a warning diagnostic, and continue processing other available backends (graceful degradation).45- Consolidate raw ticket listings:46 - Merge the raw JSON arrays into a single in-memory collection.47 - Apply global filter logic to remove completed, archived, or resolved issues.48- Output parameters:49 - `aggregated_list`: Consolidated list of active raw ticket metadata objects.50 - `failed_providers`: List of providers that failed to respond.5152### Step 3: normalize_tasks [depends_on: aggregate_ticket_payloads]53Transform heterogeneous ticket schemas into a single, standardized, unified task list:54- Standardize fields into the target schema:55 - `id`: Normalized ticket identifier string (e.g. `JIRA-101`, `PLANE-402`, `SN-INC00123`).56 - `source`: Provider identifier ("jira", "plane", or "servicenow").57 - `title`: Short title or summary string.58 - `description`: Main description body, stripped of platform-specific HTML/formatting where appropriate.59 - `status`: Normalized workflow state ("TODO", "IN_PROGRESS", "BLOCKED").60 - `priority`: Standardized severity level ("LOW", "MEDIUM", "HIGH", "CRITICAL").61 - `due_date`: ISO-8601 due date string (null if unspecified).62 - `created_date`: ISO-8601 creation timestamp.63- Sort and deduplicate:64 - Remove duplicate records if any exist.65 - Sort the task collection by priority descending, then by created_date ascending.66- Output parameters:67 - `status`: "SUCCESS" or "FAILED"68 - `normalized_tasks`: List of standard task objects containing all normalized keys.69 - `task_count`: Total number of active tickets retrieved.