@iflow-mcp/tom28881-mcp-jira-server 1.1.0

package/.env.example

@@ -0,0 +1,18 @@
+# Jira Configuration
+JIRA_HOST=https://your-company.atlassian.net
+JIRA_EMAIL=your-email@company.com
+JIRA_API_TOKEN=your-jira-api-token
+
+# Project Configuration
+JIRA_DEFAULT_PROJECT=YOUR_PROJECT_KEY
+
+# Optional: Custom Field IDs
+JIRA_FIELD_STORY_POINTS=customfield_10001
+JIRA_FIELD_ACCEPTANCE_CRITERIA=customfield_10002
+JIRA_FIELD_EPIC_LINK=customfield_10003
+
+# Optional: Auto-create test tickets for stories
+AUTO_CREATE_TEST_TICKETS=false
+
+# Optional: Default assignee
+DEFAULT_ASSIGNEE=

package/.github/workflows/ci.yml

@@ -0,0 +1,36 @@
+name: CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    
+    strategy:
+      matrix:
+        node-version: [18.x, 20.x]
+    
+    steps:
+    - uses: actions/checkout@v3
+    
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v3
+      with:
+        node-version: ${{ matrix.node-version }}
+        cache: 'npm'
+    
+    - name: Install dependencies
+      run: npm ci
+    
+    - name: Build
+      run: npm run build
+    
+    - name: Type check
+      run: npm run typecheck
+    
+    - name: Lint
+      run: npm run lint

package/CHANGELOG.md

@@ -0,0 +1,70 @@
+# 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).
+
+## [Unreleased]
+
+### Fixed
+- Fixed "Unexpected end of JSON input" error for transition-issue
+- Fixed "Cannot read properties of undefined" error for create-issue
+- Improved handling of empty API responses
+- Better error messages with context
+- Fixed link-issues with case-insensitive matching
+- Better handling of fields not available for certain issue types
+- Fixed subtask creation by properly using parent field
+- Fixed Epic-Story linking with proper error handling and guidance
+- Fixed linkTypes.map error by handling different API response structures
+- Fixed issue type validation for localized Jira instances
+
+### Added
+- Comprehensive logging system with DEBUG support
+- Automatic retry with exponential backoff (3 attempts)
+- Connection testing on startup
+- Atlassian Document Format (ADF) support for rich text
+- Convenient run.sh script for easier execution
+- Input validation with detailed error messages
+- Robust error handling for all edge cases
+- New `get-link-types` tool to list available issue link types
+- New `get-fields` tool to show available fields for project/issue type
+- New `create-epic-with-subtasks` tool for creating epics with multiple subtasks
+- New `diagnose-fields` tool to find correct custom field IDs
+- New `create-task-for-epic` tool optimized for Czech Jira
+- Smart link type matching with fallback to available types
+- Parent field support for creating subtasks
+- Detection and guidance for Epic-Story system link attempts
+- Full localization support for issue types and priorities
+- Issue type mapping for multiple languages
+
+### Improved
+- More informative startup messages
+- Better handling of test ticket creation failures
+- Enhanced transition handling with available options display
+- Enhanced debug logging for create-issue payloads
+- Link-issues now shows available types on error
+- Automatic fallback to tasks when subtasks under epics fail
+- Better handling of Czech and localized error messages
+- Issue type schema now accepts any string value for localized names
+- Priority schema now accepts any string value for localized names
+
+## [1.0.0] - 2024-12-19
+
+### Added
+- Initial release with full Jira integration
+- 7 tools for issue management (create, update, search, transition, link, comment)
+- 5 prompts for common workflows (standup, sprint planning, bug triage, release notes, epic status)
+- 5 resources for read-only data access
+- Support for custom fields (story points, acceptance criteria, epic links)
+- Automatic test ticket creation for stories
+- Comprehensive error handling and user-friendly messages
+- TypeScript implementation with full type safety
+- Environment-based configuration
+- Setup script for easy installation
+- Extensive documentation and examples
+
+### Security
+- API token authentication
+- Environment variable configuration
+- No hardcoded credentials

package/CONTRIBUTING.md

@@ -0,0 +1,102 @@
+# Contributing to MCP Jira Server
+
+Thank you for your interest in contributing! This guide will help you get started.
+
+## Getting Started
+
+1. Fork the repository
+2. Clone your fork
+3. Create a feature branch (`git checkout -b feature/amazing-feature`)
+4. Make your changes
+5. Run tests and ensure everything passes
+6. Commit your changes (`git commit -m 'Add amazing feature'`)
+7. Push to your branch (`git push origin feature/amazing-feature`)
+8. Open a Merge Request
+
+## Development Setup
+
+```bash
+# Install dependencies
+npm install
+
+# Build the project
+npm run build
+
+# Run type checking
+npm run typecheck
+
+# Run linting
+npm run lint
+```
+
+## Code Style
+
+- Use TypeScript for all new code
+- Follow existing code patterns
+- Add types for all function parameters and returns
+- Use meaningful variable and function names
+- Keep functions small and focused
+
+## Adding New Features
+
+### Adding a New Tool
+
+1. Create a new function in `src/tools/issue-tools.ts`
+2. Add Zod schema for input validation
+3. Implement the handler function
+4. Add to the exported tools object
+
+Example:
+```typescript
+const MyNewToolSchema = z.object({
+  param1: z.string(),
+  param2: z.number().optional()
+});
+
+'my-new-tool': {
+  description: 'Description of what this tool does',
+  inputSchema: zodToJsonSchema(MyNewToolSchema) as any,
+  handler: async (args: unknown) => {
+    const params = MyNewToolSchema.parse(args);
+    // Implementation
+  }
+}
+```
+
+### Adding a New Prompt
+
+1. Add to `src/prompts/jira-prompts.ts`
+2. Create input schema
+3. Return appropriate prompt messages
+
+### Adding a New Resource
+
+1. Add to `src/resources/jira-resources.ts`
+2. Implement the handler function
+3. Return data in appropriate format
+
+## Testing
+
+Currently manual testing is used. To test your changes:
+
+1. Build the project: `npm run build`
+2. Run the test script: `node test-server.js`
+3. Test with Claude Code: `claude --mcp "node dist/index.js"`
+
+## Documentation
+
+- Update README.md if adding new features
+- Add JSDoc comments to new functions
+- Include examples in documentation
+
+## Commit Messages
+
+Use clear, descriptive commit messages:
+- `feat: Add support for bulk issue updates`
+- `fix: Handle empty search results correctly`
+- `docs: Update installation instructions`
+- `refactor: Simplify error handling in JiraClient`
+
+## Questions?
+
+Feel free to open an issue for any questions or discussions!

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 MCP Jira Server Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/QUICKSTART.md

@@ -0,0 +1,107 @@
+# Quick Start Guide for Claude Code
+
+## 1. Install and Build
+
+```bash
+# Clone the repository
+git clone https://github.com/yourusername/mcp-jira-server.git
+cd mcp-jira-server
+
+# Install dependencies
+npm install
+
+# Build the project
+npm run build
+```
+
+## 2. Configure
+
+```bash
+# Run the setup script
+./setup.sh
+
+# Or manually create .env file
+cp .env.example .env
+# Edit .env with your Jira credentials
+```
+
+## 3. Run with Claude Code
+
+### Quick Test
+```bash
+# From the mcp-jira-server directory
+claude --mcp "node dist/index.js"
+```
+
+### Permanent Setup
+
+Add to `~/.claude/settings.json`:
+
+```json
+{
+  "mcpServers": [
+    {
+      "name": "jira",
+      "command": "node",
+      "args": ["/absolute/path/to/mcp-jira-server/dist/index.js"]
+    }
+  ]
+}
+```
+
+Then run:
+```bash
+claude --mcp jira
+```
+
+## 4. Example Commands
+
+Once connected, try these commands in Claude Code:
+
+### Creating Issues
+```
+Create a bug in project PROJ with high priority about login failure
+```
+
+### Searching Issues
+```
+Find all open bugs assigned to me
+```
+
+### Updating Issues
+```
+Update PROJ-123 to add 5 story points
+```
+
+### Using Prompts
+```
+Generate a standup report for my email
+```
+
+## 5. Troubleshooting
+
+### Check Server Status
+```bash
+# Test if the server starts correctly
+node test-server.js
+```
+
+### View Logs
+```bash
+# Run with debug output
+DEBUG=* claude --mcp "node dist/index.js"
+```
+
+### Common Issues
+
+1. **Authentication Failed**
+   - Verify your API token at https://id.atlassian.com/manage-profile/security/api-tokens
+   - Ensure email matches your Atlassian account
+
+2. **Project Not Found**
+   - Check project key is correct (case-sensitive)
+   - Verify you have access to the project
+
+3. **MCP Connection Failed**
+   - Ensure the server path is absolute in settings.json
+   - Check that dist/index.js exists after building