Skip to main content
Glama
CHANGELOG.md3.24 kB
# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). ## [1.6.0] - 2025-01-10 ### Added - **Markdown support**: Added optional `format` parameter to `jira_create_issue`, `jira_update_issue`, `jira_create_subtask`, and `jira_add_comment` tools - Three format options: - `markdown` (default): Automatically converts Markdown syntax to Atlassian Document Format (ADF) - `adf`: Uses description/comment as-is (assumes it's already in ADF format) - `plain`: Converts plain text to ADF with basic formatting heuristics - Backward compatible: defaults to `markdown` format - Automatic fallback to plain text if markdown conversion fails - Added `md-to-adf` package (v0.6.4) for Markdown → ADF conversion - Comprehensive test coverage for format parameter functionality (230 tests passing) - Type declarations for `md-to-adf` module ### Changed - Updated tool descriptions to reflect new format parameter - Enhanced `ensureAdfDescription` function to handle all three formats - Updated all tool schemas (Zod) to include format parameter with default value ### Technical Details - All changes maintain backward compatibility - Error handling includes fallback to plain text conversion if markdown parsing fails - Full type safety with TypeScript type definitions ## [1.5.3] - 2025-01-06 ### Fixed - Fixed `jira_get_create_meta` to properly return custom field metadata and allowed values - Changed to use classic `/issue/createmeta` endpoint with `expand` parameter for better reliability - Now correctly returns `allowedValues` for select/radio/checkbox custom fields - Fixes "Resource not found or insufficient permissions" errors on some Jira instances - Enables automated issue creation in projects with required custom fields - Simplified implementation from per-issue-type endpoint to classic endpoint ### Changed - Removed unused imports and variables to pass linter checks - Updated test suite to match new `getCreateMeta` implementation - All 222 tests passing ### Added - Documentation for `jira_get_create_meta` tool in README.md ## [1.4.0] - 2025-01-31 ### Fixed - Fixed `jira_get_issue` tool to properly extract issue keys from Jira URLs - Tool now correctly handles URLs like `https://your.atlassian.net/browse/PROJECT-123` - Extracts issue key from URL before making API call - Maintains backward compatibility with plain issue keys - Fixes 404 errors when users paste Jira URLs ### Changed - Improved URL parsing in `jira_get_issue` using existing `extractIssueKey` utility function - Enhanced test coverage for URL parsing scenarios ## [1.3.0] - Previous Release ### Added - Initial stable release with core Jira MCP tools - Support for issue management (get, create, update) - Search functionality with JQL - Project and metadata tools - Authentication with Jira Cloud API - Docker support - Comprehensive test coverage --- [1.4.0]: https://github.com/freema/mcp-jira-stdio/compare/v1.3.0...v1.4.0 [1.3.0]: https://github.com/freema/mcp-jira-stdio/releases/tag/v1.3.0

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/freema/mcp-jira-stdio'

If you have feedback or need assistance with the MCP directory API, please join our Discord server