{"format":"verfy.mcp-server/1","page":"https://verfy.dev/servers/atlassian","collectedAt":"2026-11-13","server":{"id":"atlassian","eco":"pypi","pkg":"mcp-atlassian","releases":[{"version":"0.21.0","published":"2026-03-02","started":true},{"version":"0.21.1","published":"2026-04-10","started":true},{"version":"0.22.0","published":"2026-07-10","started":true},{"version":"0.22.1","published":"2026-07-11","started":true},{"version":"0.23.0","published":"2026-07-18","started":true},{"version":"0.23.1","published":"2026-08-19","started":true},{"version":"0.24.0","published":"2026-11-08","started":true},{"version":"0.24.1","published":"2026-11-08","started":true},{"version":"0.24.2","published":"2026-11-12","started":true},{"version":"0.24.3","published":"2026-11-12","started":true}],"tools":[{"name":"jira_get_user_profile","pin":"sha256:a028e076f978f1b2bed5dc76fd337dcbd9da650cc9d1ebec289446e44ed2b506","description":"Retrieve profile information for a Jira user.\n\nUse ``user_identifier=\"me\"`` to return the account authenticated for the\ncurrent request directly from Jira's ``/myself`` endpoint. This path does\nnot require Browse Users permission."},{"name":"jira_search_assignable_users","pin":"sha256:d90ed2c762a93e66e94de0c8c8de077c70960dacb607f50519e3777bf34c9c21","description":"Search Jira users assignable in a given project or issue.\n\nUse this when you have a display name / partial name / email fragment\nand need a concrete identifier (``name`` / ``key`` for Server/DC,\n``accountId`` for Cloud) to feed into assignee, reporter, watcher, etc.\n\nReturns the full result set so the caller can disambiguate when several\nusers match — ``get_user_profile`` only resolves one identifier and is\nnot designed for human-name search.\n\nExactly one of ``project_key`` or ``issue_key`` must be provided — the\nunderlying API (``/user/assignable/search``) requires a project or issue\ncontext and works without the global \"Browse Users\" permission that bot\naccounts in locked-down DC instances often lack."},{"name":"jira_get_issue_watchers","pin":"sha256:7dd87da8ed9471695feab36038f0f6d7ab82a67e2a1cbdcdde1a90b94cdba510","description":"Get the list of watchers for a Jira issue."},{"name":"jira_add_watcher","pin":"sha256:6781ecf94f42ad083e7cb1f0ae0e4a4f4e854e141fa770f0072764075c97b737","description":"Add a user as a watcher to a Jira issue."},{"name":"jira_remove_watcher","pin":"sha256:f13aabf7c4dffa2abe13bc88e30b88ff223003ca4523358fe7aeaab230182759","description":"Remove a user from watching a Jira issue."},{"name":"jira_get_issue","pin":"sha256:f65ea5e0f5ad01397b09f0a98c5ead58a1f6fe49eaa580c807504d577cd58c87","description":"Get details of a specific Jira issue.\n\nIncludes Epic links and relationship information. Use the\n``include`` parameter to inline enrichments (remote_links,\ntransitions, watchers, changelog, comments, worklogs, epic_summary)\nso that separate tool calls are not needed. The ``epic_summary``\nsection only applies when the issue is an Epic and adds child-issue\naggregations (counts by status, assignee, and type, plus a\ncompletion percentage); it is aggregate-only unless\n``epic_summary_children`` is set."},{"name":"jira_search","pin":"sha256:ae5319d868b26976bae3a378edae5fe197cb83a790cab709b6c6a1981680a1d8","description":"Search Jira issues using JQL (Jira Query Language)."},{"name":"jira_search_fields","pin":"sha256:2e5e1e5127177553089bcb951b16fe6bfa155f13f859cde788fd9d4215e8afb5","description":"Search Jira fields by keyword with fuzzy match."},{"name":"jira_get_field_options","pin":"sha256:0b6054cce7efe79cfc95f98d3ca7416b72d8aface3b2a30f72880c0ad5944185","description":"Get allowed option values for a custom field.\n\nReturns the list of valid options for select, multi-select, radio,\ncheckbox, and cascading select custom fields.\n\nCloud: Uses the Field Context Option API. If context_id is not provided,\nautomatically resolves to the global context.\n\nServer/DC: Uses createmeta to get allowedValues. Requires project_key\nand issue_type parameters."},{"name":"jira_get_project_issues","pin":"sha256:29c9e086c8ce10941bf90791a4c41ad878210d6a8136946d538c8553dd076cee","description":"Get all issues for a specific Jira project."},{"name":"jira_get_transitions","pin":"sha256:61ceec29a95d275e53b7ae94c5e40eac9d9af0a865b44428f27bf84310f5f56a","description":"Get available status transitions for a Jira issue."},{"name":"jira_get_worklog","pin":"sha256:7229af3c22d25043783b1b8311f6b7e965a252ca1131199963a6e491bdb6143b","description":"Get worklog entries for a Jira issue."},{"name":"jira_download_attachments","pin":"sha256:2a82203e04a06c21540fe1db01dcb6c7974104f94a42e474d9cedfa166b5b0e3","description":"Download attachments from a Jira issue.\n\nReturns attachment contents as base64-encoded content so that they are\navailable over the MCP protocol without requiring filesystem access on\nthe server. Image attachments are returned as ``EmbeddedResource`` blobs;\nall other attachments (documents, archives, etc.) are returned as\n``TextContent`` carrying a base64 payload, since many MCP clients only\nforward ``EmbeddedResource`` blobs for recognized image MIME types and\notherwise drop the attachment (#1419)."},{"name":"jira_get_issue_images","pin":"sha256:153bae279e5bd999d4e0de1304d67d623ad8d2d3bab6435b2b8a3b50738a37fd","description":"Get all images attached to a Jira issue as inline image content.\n\nFilters attachments to images only (PNG, JPEG, GIF, WebP, SVG, BMP)\nand returns them as base64-encoded ImageContent that clients can\nrender directly. Non-image attachments are excluded.\n\nFiles with ambiguous MIME types (application/octet-stream) are\ndetected by filename extension as a fallback. Images larger than\n50 MB are skipped with an error entry in the summary."},{"name":"jira_get_agile_boards","pin":"sha256:d6162c0194d6bdc99bd72c547506590251fb610cf6680d3c05f9db16f3789d47","description":"Get jira agile boards by name, project key, or type."},{"name":"jira_get_board_issues","pin":"sha256:7ad7f96aa4161e1db2de5d9475bf8bde3f87e6f033cc63e168578df771a9867b","description":"Get all issues linked to a specific board filtered by JQL."},{"name":"jira_get_sprints_from_board","pin":"sha256:854765a79406fa171234b073de52acb7f6c8d6d153bdab09d470d1ad2f29add2","description":"Get jira sprints from board by state."},{"name":"jira_get_sprint_issues","pin":"sha256:089fbae46787a76295f65705e4dc5b6b18145a199ff7a2ef08185ca9fa6e28a7","description":"Get jira issues from sprint."},{"name":"jira_get_link_types","pin":"sha256:ee4764575005102d9f8a84d83d264d8e84915ba47dca03b5767a4f8c9ff9c977","description":"Get all available issue link types."},{"name":"jira_create_issue","pin":"sha256:3a24b27ae911450c94a71352dd8c03ab4cdc19aeb7f12a8fc5bbf1f2efc00977","description":"Create a new Jira issue with optional Epic link or parent for subtasks."},{"name":"jira_batch_create_issues","pin":"sha256:25a85f021687aee3df9a974feee420752137b0fe49b5d19e97130f4418f95780","description":"Create multiple Jira issues in a batch."},{"name":"jira_batch_get_changelogs","pin":"sha256:e7cd05d18261b621801fa0efbfe57ccd84d04d4b57b02d7525cfc18b6544ccd3","description":"Get changelogs for multiple Jira issues (Cloud only)."},{"name":"jira_update_issue","pin":"sha256:5e9c5f85c1bd140bf947db8d43459d094197301b9c862e00851eab16691494d1","description":"Update an issue and optionally transition, comment, and log work."},{"name":"jira_assign_issue","pin":"sha256:e1b8efbd1b7079d3908136c8e313716ca4b3c98990ec0ee311e14ad51c19f286","description":"Assign a Jira issue to a user using the dedicated assignment endpoint.\n\nThis is more reliable than setting assignee via update_issue, which is\nsilently ignored by some Jira configurations. Uses PUT /issue/{key}/assignee.\n\nOn Jira Server/DC the following identifier forms are all accepted:\nlogin name, email address, display name, or JIRAUSER key. The resolution\norder is: key lookup → email search (with email-as-username fallback) →\ntext search → assignable-user search scoped to the issue."},{"name":"jira_delete_issue","pin":"sha256:230f7af9db9c0b0190bf6fb1d00d36df409ffdf615f2b2fb553948c7fa8f497f","description":"Delete an existing Jira issue."},{"name":"jira_move_issue","pin":"sha256:8ca931bc419924d0158913bcde117de5a5a1a33211a0f3d503ecd94ebf87ece1","description":"Move a Jira issue to a different project (Jira Cloud only).\n\nUses Jira Cloud's bulk move API to perform a cross-project move.\nThe issue keeps its current issue type and may be assigned a new key in the\ntarget project (e.g., OLDPROJ-123 becomes NEWPROJ-456).\n\nThe move is processed asynchronously on Jira's side; this tool polls\nuntil confirmed or times out after 30 seconds."},{"name":"jira_add_comment","pin":"sha256:92286e5e5310e62b8d0717e83a6da65c234e8483c26077aef1cfa042c5dbfd0b","description":"Add a comment to a Jira issue."},{"name":"jira_edit_comment","pin":"sha256:ab0b55226c7499293962204a64ebb77530541c73fd5f52d5d8138922d5239369","description":"Edit an existing comment on a Jira issue."},{"name":"jira_add_worklog","pin":"sha256:6cffa4a301778db2aef35d8b43177bba7f7a948a86fe8257baf911b89b7d3acf","description":"Add a worklog entry to a Jira issue."},{"name":"jira_link_to_epic","pin":"sha256:47c8ecc2f4d27e67c9edef7abe5b45df0869a5a011435b985be05a52d35c283e","description":"Link an existing issue to an epic."},{"name":"jira_create_issue_link","pin":"sha256:7667f99ffe75016dbe10cbe05caa1b4cfa698716a5b400c7e62a361f702eb55c","description":"Create a link between two Jira issues."},{"name":"jira_create_remote_issue_link","pin":"sha256:b209a33652379594bfb82b0c20d674474e4ce12d294ec8a136de02a07716c9e1","description":"Create a remote issue link (web link or Confluence link) for a Jira issue.\n\nThis tool allows you to add web links and Confluence links to Jira issues.\nThe links will appear in the issue's \"Links\" section and can be clicked to navigate to external resources."},{"name":"jira_remove_issue_link","pin":"sha256:7f5e220cd386a3434419d4d867500e7f515252d9ba6980aae42775c8bff6c2b9","description":"Remove a link between two Jira issues."},{"name":"jira_transition_issue","pin":"sha256:899ce2ae46438d45dfdacc59425781d8823ffc5918bdb64e6e3a69eac9a1be24","description":"Transition a Jira issue to a new status."},{"name":"jira_create_sprint","pin":"sha256:7832f64de4b8f077c8e04b9763d469bd920c9ed46dc417210ac551cb3c69501a","description":"Create Jira sprint for a board."},{"name":"jira_update_sprint","pin":"sha256:99365c252b534633d643206f0d2750aa0478ed98f54333b1f6dc977e21f4bf58","description":"Update jira sprint."},{"name":"jira_add_issues_to_sprint","pin":"sha256:cb4e95fea19b46bf8372a05dc7bf8857085d8462018eaf723b7e24c1e70a0e58","description":"Add issues to a Jira sprint."},{"name":"jira_move_issues_to_backlog","pin":"sha256:2490f9a9d352f33eef91a573ffafc1047aab5a922d2a18265e9803905a5c1d68","description":"Move issues to the backlog, removing them from any sprint."},{"name":"jira_get_project_issue_types","pin":"sha256:ebc07fa468e77b582b60a24ed63e2951e50eaec331663d52fcd54c33ec6230bf","description":"Get available issue types for a Jira project.\n\nReturns the list of issue types (Bug, Task, Story, Epic, etc.) that can\nbe created in the specified project. Use the returned issue type IDs with\nget_create_fields to discover what fields each type requires."},{"name":"jira_get_create_fields","pin":"sha256:8b603334744f4b893ab93b19be7cbccd21b52e0aa5491597fd553a08ea836021","description":"Get fields available for creating an issue of a specific type.\n\nReturns all fields (required and optional) for the given project and\nissue type, including field names, IDs, whether they're required, and\ntheir schema. Use jira_get_field_options when a returned field needs its\nallowed values."},{"name":"jira_get_project_versions","pin":"sha256:978eb60c6ed6994d0ef2ee94706af18846608604ef1971189083f8d397b89570","description":"Get all fix versions for a specific Jira project."},{"name":"jira_get_project_components","pin":"sha256:124daf0fc6b2bae36e299fa374a6a0c14aeb9ed8d9f664ac4bad7d6a35cc9ed0","description":"Get all components for a specific Jira project."},{"name":"jira_get_all_projects","pin":"sha256:c1fb94b371f01c87f3fc7ca7da6d6412deb10b337b80b5fa57addef98aa59a54","description":"Get all Jira projects accessible to the current user."},{"name":"jira_search_projects","pin":"sha256:dc647cc657292702d4840c9ba7e25654d6c3007dfe0ce0d8ffda52ee37535097","description":"Search for Jira projects by name or key prefix.\n\nUses the projects picker endpoint to return a ranked list of matching\nprojects without fetching every visible project on the instance."},{"name":"jira_get_project_fields","pin":"sha256:53f6f8c57faec2b63678bdcca6c12db21b31f0a923d6ed576c61fbb53245e174","description":"Get the fields available on issues of a project (the create schema),\ndeduplicated across the project's issue types — i.e. which fields tickets in\nthis project have, regardless of whether they are filled."},{"name":"jira_get_service_desk_for_project","pin":"sha256:48042cbed908b2ef9253993cb2eb70cedea8f30065e51b854ab8c303773fd56a","description":"Get the Jira Service Desk associated with a project key.\n\nServer/Data Center only. Not available on Jira Cloud."},{"name":"jira_get_service_desk_queues","pin":"sha256:9b389b0b4302e972389a13ce1b20039f012ca8d1045e87a5bc48146279b82c4a","description":"Get queues for a Jira Service Desk.\n\nServer/Data Center only. Not available on Jira Cloud."},{"name":"jira_get_queue_issues","pin":"sha256:2f012b2375814a988c9f215e80a7162b96ed0253b82667a8432a8615c4d1796a","description":"Get issues from a Jira Service Desk queue.\n\nServer/Data Center only. Not available on Jira Cloud."},{"name":"jira_get_request_types","pin":"sha256:855e3d6cfe70a24fe9df53c230c3286d0517f8264284f587e0b1bdbdee50ea19","description":"Get request types for a Jira Service Management service desk."},{"name":"jira_get_request_type_fields","pin":"sha256:e43c6dca09d2532d91f9dcc75551804fd22ace1aeb86259a7270b84d74ae5f2d","description":"Get field definitions for a Jira Service Management request type."},{"name":"jira_create_customer_request","pin":"sha256:a9e9a3b2136b08d7c05e53aafe81f2d53026fabcdb15a8c366237af1fda9c8a2","description":"Create a Jira Service Management customer request."},{"name":"jira_create_version","pin":"sha256:9201fc46045baaf904478b2cc475dbffd288eff691313ed8ca137cbedc3cb84c","description":"Create a new fix version in a Jira project."},{"name":"jira_batch_create_versions","pin":"sha256:e5c9694ba41dea8bab9a3a3a863289e46a691a8a69203c54b5e8fd5d7126f4b5","description":"Batch create multiple versions in a Jira project."},{"name":"jira_update_version","pin":"sha256:bea2651e8e27e2fbc1d09797de4da34cae124d3738933c8aaecd7facd5e37eaa","description":"Update an existing fix version in a Jira project.\n\nOnly fields explicitly provided are modified; other attributes of the\nversion are left untouched. Useful for archiving/unarchiving versions,\nrenaming, or shifting release dates without recreating them."},{"name":"jira_get_issue_proforma_forms","pin":"sha256:c4d77461bac42d54aa4412c958962e9757d536393a5bbc2a866c062e51f88368","description":"Get all ProForma forms associated with a Jira issue.\n\nUses the new Jira Forms REST API. Form IDs are returned as UUIDs."},{"name":"jira_get_proforma_form_details","pin":"sha256:7eb1563c4970f0c4ee4f0f8dbe670b9938c78173322b2c18752bc57be1703ef6","description":"Get detailed information about a specific ProForma form.\n\nUses the new Jira Forms REST API. Returns form details including ADF design structure."},{"name":"jira_update_proforma_form_answers","pin":"sha256:7096066d924a8dec71e610ee0907ab17589a2044fac185ac8dd3f8e2b98ca4c6","description":"Update form field answers using the Jira Forms REST API.\n\nThis is the primary method for updating form data. Each answer object\nmust specify the question ID, answer type, and value.\n\n**⚠️ KNOWN LIMITATION - DATETIME fields:**\nThe Jira Forms API does NOT properly preserve time components in DATETIME fields.\nOnly the date portion is stored; times are reset to midnight (00:00:00).\n\n**Workaround for DATETIME fields:**\nUse jira_update_issue to directly update the underlying custom fields instead:\n1. Get the custom field ID from the form details (question's \"jiraField\" property)\n2. Use jira_update_issue with fields like: {\"customfield_XXXXX\": \"2026-01-09T11:50:00-08:00\"}\n\nExample:\n```python\n# Instead of updating via form (loses time):\n# jira_update_proforma_form_answers(issue_key, form_id, [{\"questionId\": \"91\", \"type\": \"DATETIME\", \"value\": \"...\"}])\n\n# Use direct field update (preserves time):\njira_update_issue(issue_key, {\"customfield_10542\": \"2026-01-09T11:50:00-08:00\"})\n```\n\n**Automatic DateTime Conversion:**\nFor DATE and DATETIME fields, you can provide values as:\n- ISO 8601 strings (e.g., \"2024-12-17T19:00:00Z\", \"2024-12-17\")\n- Unix timestamps in milliseconds (e.g., 1734465600000)\n\nThe tool automatically converts ISO 8601 strings to Unix timestamps.\n\nExample answers:\n[\n    {\"questionId\": \"q1\", \"type\": \"TEXT\", \"value\": \"Updated description\"},\n    {\"questionId\": \"q2\", \"type\": \"SELECT\", \"value\": \"Product A\"},\n    {\"questionId\": \"q3\", \"type\": \"NUMBER\", \"value\": 42},\n    {\"questionId\": \"q4\", \"type\": \"DATE\", \"value\": \"2024-12-17\"}\n]\n\nCommon answer types:\n- TEXT: String values\n- NUMBER: Numeric values\n- DATE: Date values (ISO 8601 string or Unix timestamp in ms)\n- DATETIME: DateTime values - ⚠️ USE WORKAROUND ABOVE\n- SELECT: Single selection from options\n- MULTI_SELECT: Multiple selections (value as list)\n- CHECKBOX: Boolean values"},{"name":"jira_get_issue_dates","pin":"sha256:f2c9650bdfc751c670cc67289863dde68cbb70e891f0ad6fae9e6ec4351b345c","description":"Get date information and status transition history for a Jira issue.\n\nReturns dates (created, updated, due date, resolution date) and optionally\nstatus change history with time tracking for workflow analysis."},{"name":"jira_get_issue_sla","pin":"sha256:c540b5f91743095dd17f50fc05a55e24cbf37ab88d6aeebaeb17794c868539cb","description":"Calculate SLA metrics for a Jira issue.\n\nComputes various time-based metrics including cycle time, lead time,\ntime spent in each status, due date compliance, and more.\n\nWorking hours can be configured via environment variables:\n- JIRA_SLA_WORKING_HOURS_ONLY: Enable working hours filtering (true/false)\n- JIRA_SLA_WORKING_HOURS_START: Start time (e.g., \"09:00\")\n- JIRA_SLA_WORKING_HOURS_END: End time (e.g., \"17:00\")\n- JIRA_SLA_WORKING_DAYS: Working days (e.g., \"1,2,3,4,5\" for Mon-Fri)\n- JIRA_SLA_TIMEZONE: Timezone for calculations (e.g., \"America/New_York\")"},{"name":"jira_get_issue_development_info","pin":"sha256:580f1942b60b8408206ef4ba158b8a0dfdd7fcc52f71444c38cbf5bf03b0338a","description":"Get development information (PRs, commits, branches) linked to a Jira issue.\n\nThis retrieves the development panel information that shows linked\npull requests, branches, and commits from connected source control systems\nlike Bitbucket, GitHub, or GitLab."},{"name":"jira_get_issues_development_info","pin":"sha256:17f40182fa6f859717cda4567c73d7ffb0ccd63886b9c279eb9402ffa2997a9c","description":"Get development information for multiple Jira issues.\n\nBatch retrieves development panel information (PRs, commits, branches)\nfor multiple issues at once."},{"name":"jira_get_project_epic_hierarchy","pin":"sha256:207344e93a1706ce526f278bb1ade8a9d66ec02728b403cd43fda124de861054","description":"Group a project's epics under their cross-project parent issues.\n\nFetches all epics in the project, detects their parent issue via\nthe parent field or inward issue links, then groups them by parent.\nEpics with no detected parent appear under \"Unlinked\". Useful for\nunderstanding how a project's epics roll up to initiatives in\nanother project."},{"name":"jira_get_cross_project_dependencies","pin":"sha256:4300bd7096fa37ab821587f2bc983a68b962a1425008631b9f41cd2551e0f8fe","description":"Find all cross-project issue links for a project.\n\nScans issues in the project, extracts every issue link whose\ntarget belongs to a different project, and groups them by target\nproject and link type. Useful for dependency analysis across\nmulti-project Jira setups."}],"updates":[{"from":"0.21.0","to":"0.21.1","published":"2026-04-10","bump":"patch","added":[],"removed":[],"changed":[{"tool":"jira_get_board_issues","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issue","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_sprint_issues","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_search","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]}]},{"from":"0.21.1","to":"0.22.0","published":"2026-07-10","bump":"minor","added":["jira_assign_issue","jira_get_create_fields","jira_get_project_fields","jira_get_project_issue_types","jira_move_issue","jira_move_issues_to_backlog","jira_search_assignable_users","jira_search_projects","jira_update_version"],"removed":[],"changed":[{"tool":"jira_get_board_issues","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issue","description":true,"schema":true,"before":"Get details of a specific Jira issue including its Epic links and relationship information.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n    fields: Comma-separated list of fields to return (e.g., 'summary,status,customfield_10010'), a single field as a string (e.g., 'duedate'), '*all' for all fields, or omitted for essentials.\n    expand: Optional fields to expand.\n    comment_limit: Maximum number of comments.\n    properties: Issue properties to return.\n    update_history: Whether to update issue view history.\n\nReturns:\n    JSON string representing the Jira issue object.\n\nRaises:\n    ValueError: If the Jira client is not configured or available.","after":"Get details of a specific Jira issue.\n\nIncludes Epic links and relationship information. Use the\n``include`` parameter to inline enrichments (remote_links,\ntransitions, watchers, changelog, comments, worklogs) so that\nseparate tool calls are not needed.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n    fields: Comma-separated fields to return.\n    expand: Optional fields to expand.\n    comment_limit: Maximum number of comments.\n    properties: Issue properties to return.\n    update_history: Whether to update issue view history.\n    include: Comma-separated enrichment sections to inline.\n\nReturns:\n    JSON string representing the Jira issue object.\n\nRaises:\n    ValueError: If the Jira client is not configured.","propsAdded":["include"],"propsRemoved":[]},{"tool":"jira_get_issue_development_info","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issues_development_info","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_sprint_issues","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_search","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]}]},{"from":"0.22.0","to":"0.22.1","published":"2026-07-11","bump":"patch","added":[],"removed":[],"changed":[{"tool":"jira_get_board_issues","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issue","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_sprint_issues","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_search","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]}]},{"from":"0.22.1","to":"0.23.0","published":"2026-07-18","bump":"minor","added":["jira_create_customer_request","jira_get_cross_project_dependencies","jira_get_project_epic_hierarchy","jira_get_request_type_fields","jira_get_request_types"],"removed":[],"changed":[{"tool":"jira_add_comment","description":true,"schema":true,"before":"Add a comment to a Jira issue.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n    body: Comment text in Markdown.\n    visibility: (Optional) Comment visibility as JSON string.\n    public: (Optional) For JSM issues. True = customer-visible,\n        False = internal/agent-only. Uses ServiceDesk API.\n\nReturns:\n    JSON string representing the added comment object.\n\nRaises:\n    ValueError: If in read-only mode or Jira client unavailable.","after":"Add a comment to a Jira issue.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_add_issues_to_sprint","description":true,"schema":true,"before":"Add issues to a Jira sprint.\n\nArgs:\n    ctx: The FastMCP context.\n    sprint_id: The ID of the sprint.\n    issue_keys: Comma-separated issue keys.\n\nReturns:\n    JSON string with success message.\n\nRaises:\n    ValueError: If in read-only mode or Jira client unavailable.","after":"Add issues to a Jira sprint.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_add_watcher","description":true,"schema":true,"before":"Add a user as a watcher to a Jira issue.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n    user_identifier: Account ID (Cloud) or username (Server/DC).\n\nReturns:\n    JSON string with success confirmation.\n\nRaises:\n    ValueError: If the Jira client is not configured or available.","after":"Add a user as a watcher to a Jira issue.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_add_worklog","description":true,"schema":true,"before":"Add a worklog entry to a Jira issue.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n    time_spent: Time spent in Jira format.\n    comment: Optional comment in Markdown.\n    started: Optional start time in ISO format.\n    original_estimate: Optional new original estimate.\n    remaining_estimate: Optional new remaining estimate.\n\n\nReturns:\n    JSON string representing the added worklog object.\n\nRaises:\n    ValueError: If in read-only mode or Jira client unavailable.","after":"Add a worklog entry to a Jira issue.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_assign_issue","description":true,"schema":true,"before":"Assign a Jira issue to a user using the dedicated assignment endpoint.\n\nThis is more reliable than setting assignee via update_issue, which is\nsilently ignored by some Jira configurations. Uses PUT /issue/{key}/assignee.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n    assignee: User identifier (email, display name, or account ID), or a\n        JSON object string from jira_search_assignable_users. Pass None or\n        empty string to unassign.\n\nReturns:\n    JSON string representing the updated issue object.\n\nRaises:\n    ValueError: If in read-only mode, Jira client unavailable, or user not found.","after":"Assign a Jira issue to a user using the dedicated assignment endpoint.\n\nThis is more reliable than setting assignee via update_issue, which is\nsilently ignored by some Jira configurations. Uses PUT /issue/{key}/assignee.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_batch_create_issues","description":true,"schema":true,"before":"Create multiple Jira issues in a batch.\n\nArgs:\n    ctx: The FastMCP context.\n    issues: JSON array string of issue objects.\n    validate_only: If true, only validates without creating.\n\nReturns:\n    JSON string indicating success and listing created issues (or validation result).\n\nRaises:\n    ValueError: If in read-only mode, Jira client unavailable, or invalid JSON.","after":"Create multiple Jira issues in a batch.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_batch_create_versions","description":true,"schema":true,"before":"Batch create multiple versions in a Jira project.\n\nArgs:\n    ctx: The FastMCP context.\n    project_key: The project key.\n    versions: JSON array string of version objects.\n\nReturns:\n    JSON array of results, each with success flag, version or error.","after":"Batch create multiple versions in a Jira project.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_batch_get_changelogs","description":true,"schema":true,"before":"Get changelogs for multiple Jira issues (Cloud only).\n\nArgs:\n    ctx: The FastMCP context.\n    issue_ids_or_keys: List of issue IDs or keys.\n    fields: List of fields to filter changelogs by. None for all fields.\n    limit: Maximum changelogs per issue (-1 for all).\n\nReturns:\n    JSON string representing a list of issues with their changelogs.\n\nRaises:\n    NotImplementedError: If run on Jira Server/Data Center.\n    ValueError: If Jira client is unavailable.","after":"Get changelogs for multiple Jira issues (Cloud only).","propsAdded":[],"propsRemoved":[]},{"tool":"jira_create_issue","description":true,"schema":true,"before":"Create a new Jira issue with optional Epic link or parent for subtasks.\n\nArgs:\n    ctx: The FastMCP context.\n    project_key: The JIRA project key.\n    summary: Summary/title of the issue.\n    issue_type: Issue type (e.g., 'Task', 'Bug', 'Story', 'Epic', 'Subtask').\n    assignee: Assignee's user identifier (string): Email, display name, or account ID (e.g., 'user@example.com', 'John Doe', 'accountid:...').\n    description: Issue description in Markdown format.\n    components: Comma-separated list of component names.\n    additional_fields: JSON string of additional fields.\n\nReturns:\n    JSON string representing the created issue object.\n\nRaises:\n    ValueError: If in read-only mode or Jira client is unavailable.","after":"Create a new Jira issue with optional Epic link or parent for subtasks.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_create_issue_link","description":true,"schema":true,"before":"Create a link between two Jira issues.\n\nArgs:\n    ctx: The FastMCP context.\n    link_type: The type of link (e.g., 'Blocks').\n    inward_issue_key: The key of the source issue.\n    outward_issue_key: The key of the target issue.\n    comment: Optional comment text.\n    comment_visibility: Optional JSON string for comment visibility.\n\nReturns:\n    JSON string indicating success or failure.\n\nRaises:\n    ValueError: If required fields are missing, invalid input, in read-only mode, or Jira client unavailable.","after":"Create a link between two Jira issues.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_create_remote_issue_link","description":true,"schema":true,"before":"Create a remote issue link (web link or Confluence link) for a Jira issue.\n\nThis tool allows you to add web links and Confluence links to Jira issues.\nThe links will appear in the issue's \"Links\" section and can be clicked to navigate to external resources.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: The key of the issue to add the link to.\n    url: The URL to link to (can be any web page or Confluence page).\n    title: The title/name that will be displayed for the link.\n    summary: Optional description of what the link is for.\n    relationship: Optional relationship description.\n    icon_url: Optional URL to a 16x16 icon for the link.\n\nReturns:\n    JSON string indicating success or failure.\n\nRaises:\n    ValueError: If required fields are missing, invalid input, in read-only mode, or Jira client unavailable.","after":"Create a remote issue link (web link or Confluence link) for a Jira issue.\n\nThis tool allows you to add web links and Confluence links to Jira issues.\nThe links will appear in the issue's \"Links\" section and can be clicked to navigate to external resources.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_create_sprint","description":true,"schema":true,"before":"Create Jira sprint for a board.\n\nArgs:\n    ctx: The FastMCP context.\n    board_id: Board ID.\n    name: Sprint name.\n    start_date: Start date (ISO format).\n    end_date: End date (ISO format).\n    goal: Optional sprint goal.\n\nReturns:\n    JSON string representing the created sprint object.\n\nRaises:\n    ValueError: If in read-only mode or Jira client unavailable.","after":"Create Jira sprint for a board.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_create_version","description":true,"schema":true,"before":"Create a new fix version in a Jira project.\n\nArgs:\n    ctx: The FastMCP context.\n    project_key: The project key.\n    name: Name of the version.\n    start_date: Start date (optional).\n    release_date: Release date (optional).\n    description: Description (optional).\n\nReturns:\n    JSON string of the created version object.","after":"Create a new fix version in a Jira project.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_delete_issue","description":true,"schema":true,"before":"Delete an existing Jira issue.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n\nReturns:\n    JSON string indicating success.\n\nRaises:\n    ValueError: If in read-only mode or Jira client unavailable.","after":"Delete an existing Jira issue.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_download_attachments","description":true,"schema":true,"before":"Download attachments from a Jira issue.\n\nReturns attachment contents as base64-encoded embedded resources so that\nthey are available over the MCP protocol without requiring filesystem\naccess on the server.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n\nReturns:\n    A list containing a text summary and one EmbeddedResource per\n    successfully downloaded attachment.","after":"Download attachments from a Jira issue.\n\nReturns attachment contents as base64-encoded content so that they are\navailable over the MCP protocol without requiring filesystem access on\nthe server. Image attachments are returned as ``EmbeddedResource`` blobs;\nall other attachments (documents, archives, etc.) are returned as\n``TextContent`` carrying a base64 payload, since many MCP clients only\nforward ``EmbeddedResource`` blobs for recognized image MIME types and\notherwise drop the attachment (#1419).","propsAdded":[],"propsRemoved":[]},{"tool":"jira_edit_comment","description":true,"schema":true,"before":"Edit an existing comment on a Jira issue.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n    comment_id: The ID of the comment to edit.\n    body: Updated comment text in Markdown.\n    visibility: (Optional) Comment visibility as JSON string.\n\nReturns:\n    JSON string representing the updated comment object.\n\nRaises:\n    ValueError: If in read-only mode or Jira client unavailable.","after":"Edit an existing comment on a Jira issue.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_agile_boards","description":true,"schema":true,"before":"Get jira agile boards by name, project key, or type.\n\nArgs:\n    ctx: The FastMCP context.\n    board_name: Name of the board (fuzzy search).\n    project_key: Project key.\n    board_type: Board type ('scrum' or 'kanban').\n    start_at: Starting index.\n    limit: Maximum results.\n\nReturns:\n    JSON string representing a list of board objects.","after":"Get jira agile boards by name, project key, or type.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_all_projects","description":true,"schema":true,"before":"Get all Jira projects accessible to the current user.\n\nArgs:\n    ctx: The FastMCP context.\n    include_archived: Whether to include archived projects.\n\nReturns:\n    JSON string representing a list of project objects accessible to the user.\n    Project keys are always returned in uppercase.\n    If JIRA_PROJECTS_FILTER is configured, only returns projects matching those keys.\n\nRaises:\n    ValueError: If the Jira client is not configured or available.","after":"Get all Jira projects accessible to the current user.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_board_issues","description":true,"schema":true,"before":"Get all issues linked to a specific board filtered by JQL.\n\nArgs:\n    ctx: The FastMCP context.\n    board_id: The ID of the board.\n    jql: JQL query string to filter issues.\n    fields: Comma-separated fields to return.\n    start_at: Starting index for pagination.\n    limit: Maximum number of results.\n    expand: Optional fields to expand.\n\nReturns:\n    JSON string representing the search results including pagination info.","after":"Get all issues linked to a specific board filtered by JQL.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_create_fields","description":true,"schema":true,"before":"Get fields available for creating an issue of a specific type.\n\nReturns all fields (required and optional) for the given project and\nissue type, including field names, IDs, whether they're required, and\ntheir schema. Use jira_get_field_options when a returned field needs its\nallowed values.\n\nArgs:\n    ctx: The FastMCP context.\n    project_key: The project key.\n    issue_type_id: The issue type ID.\n\nReturns:\n    JSON string with list of field metadata (field_id, name, required, schema).","after":"Get fields available for creating an issue of a specific type.\n\nReturns all fields (required and optional) for the given project and\nissue type, including field names, IDs, whether they're required, and\ntheir schema. Use jira_get_field_options when a returned field needs its\nallowed values.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_field_options","description":true,"schema":true,"before":"Get allowed option values for a custom field.\n\nReturns the list of valid options for select, multi-select, radio,\ncheckbox, and cascading select custom fields.\n\nCloud: Uses the Field Context Option API. If context_id is not provided,\nautomatically resolves to the global context.\n\nServer/DC: Uses createmeta to get allowedValues. Requires project_key\nand issue_type parameters.\n\nArgs:\n    ctx: The FastMCP context.\n    field_id: The custom field ID.\n    context_id: Field context ID (Cloud only, auto-resolved if omitted).\n    project_key: Project key (required for Server/DC).\n    issue_type: Issue type name (required for Server/DC).\n    contains: Case-insensitive substring filter on option values.\n    return_limit: Cap on number of results after filtering.\n    values_only: Return compact format with only value strings.\n\nReturns:\n    JSON string with the list of available options.","after":"Get allowed option values for a custom field.\n\nReturns the list of valid options for select, multi-select, radio,\ncheckbox, and cascading select custom fields.\n\nCloud: Uses the Field Context Option API. If context_id is not provided,\nautomatically resolves to the global context.\n\nServer/DC: Uses createmeta to get allowedValues. Requires project_key\nand issue_type parameters.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issue","description":true,"schema":true,"before":"Get details of a specific Jira issue.\n\nIncludes Epic links and relationship information. Use the\n``include`` parameter to inline enrichments (remote_links,\ntransitions, watchers, changelog, comments, worklogs) so that\nseparate tool calls are not needed.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n    fields: Comma-separated fields to return.\n    expand: Optional fields to expand.\n    comment_limit: Maximum number of comments.\n    properties: Issue properties to return.\n    update_history: Whether to update issue view history.\n    include: Comma-separated enrichment sections to inline.\n\nReturns:\n    JSON string representing the Jira issue object.\n\nRaises:\n    ValueError: If the Jira client is not configured.","after":"Get details of a specific Jira issue.\n\nIncludes Epic links and relationship information. Use the\n``include`` parameter to inline enrichments (remote_links,\ntransitions, watchers, changelog, comments, worklogs) so that\nseparate tool calls are not needed.","propsAdded":["use_display_names"],"propsRemoved":[]},{"tool":"jira_get_issue_dates","description":true,"schema":true,"before":"Get date information and status transition history for a Jira issue.\n\nReturns dates (created, updated, due date, resolution date) and optionally\nstatus change history with time tracking for workflow analysis.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: The Jira issue key.\n    include_status_changes: Whether to include status change history.\n    include_status_summary: Whether to include aggregated time per status.\n\nReturns:\n    JSON string with issue dates and optional status tracking data.","after":"Get date information and status transition history for a Jira issue.\n\nReturns dates (created, updated, due date, resolution date) and optionally\nstatus change history with time tracking for workflow analysis.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issue_development_info","description":true,"schema":true,"before":"Get development information (PRs, commits, branches) linked to a Jira issue.\n\nThis retrieves the development panel information that shows linked\npull requests, branches, and commits from connected source control systems\nlike Bitbucket, GitHub, or GitLab.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: The Jira issue key.\n    application_type: Optional filter by source control type.\n    data_type: Optional filter by data type (pullrequest, branch, etc.).\n\nReturns:\n    JSON string with development information including:\n    - pullRequests: List of linked pull requests with status, author, reviewers\n    - branches: List of linked branches\n    - commits: List of linked commits\n    - repositories: List of repositories involved","after":"Get development information (PRs, commits, branches) linked to a Jira issue.\n\nThis retrieves the development panel information that shows linked\npull requests, branches, and commits from connected source control systems\nlike Bitbucket, GitHub, or GitLab.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issue_images","description":true,"schema":true,"before":"Get all images attached to a Jira issue as inline image content.\n\nFilters attachments to images only (PNG, JPEG, GIF, WebP, SVG, BMP)\nand returns them as base64-encoded ImageContent that clients can\nrender directly. Non-image attachments are excluded.\n\nFiles with ambiguous MIME types (application/octet-stream) are\ndetected by filename extension as a fallback. Images larger than\n50 MB are skipped with an error entry in the summary.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n\nReturns:\n    A list with a text summary followed by one ImageContent per\n    successfully downloaded image.","after":"Get all images attached to a Jira issue as inline image content.\n\nFilters attachments to images only (PNG, JPEG, GIF, WebP, SVG, BMP)\nand returns them as base64-encoded ImageContent that clients can\nrender directly. Non-image attachments are excluded.\n\nFiles with ambiguous MIME types (application/octet-stream) are\ndetected by filename extension as a fallback. Images larger than\n50 MB are skipped with an error entry in the summary.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issue_proforma_forms","description":true,"schema":true,"before":"Get all ProForma forms associated with a Jira issue.\n\nUses the new Jira Forms REST API. Form IDs are returned as UUIDs.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: The issue key to get forms for.\n\nReturns:\n    JSON string representing the list of ProForma forms, or an error object if failed.","after":"Get all ProForma forms associated with a Jira issue.\n\nUses the new Jira Forms REST API. Form IDs are returned as UUIDs.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issue_sla","description":true,"schema":true,"before":"Calculate SLA metrics for a Jira issue.\n\nComputes various time-based metrics including cycle time, lead time,\ntime spent in each status, due date compliance, and more.\n\nWorking hours can be configured via environment variables:\n- JIRA_SLA_WORKING_HOURS_ONLY: Enable working hours filtering (true/false)\n- JIRA_SLA_WORKING_HOURS_START: Start time (e.g., \"09:00\")\n- JIRA_SLA_WORKING_HOURS_END: End time (e.g., \"17:00\")\n- JIRA_SLA_WORKING_DAYS: Working days (e.g., \"1,2,3,4,5\" for Mon-Fri)\n- JIRA_SLA_TIMEZONE: Timezone for calculations (e.g., \"America/New_York\")\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: The Jira issue key.\n    metrics: Comma-separated list of metrics to calculate.\n    working_hours_only: Use working hours only for calculations.\n    include_raw_dates: Include raw date values in response.\n\nReturns:\n    JSON string with calculated SLA metrics.","after":"Calculate SLA metrics for a Jira issue.\n\nComputes various time-based metrics including cycle time, lead time,\ntime spent in each status, due date compliance, and more.\n\nWorking hours can be configured via environment variables:\n- JIRA_SLA_WORKING_HOURS_ONLY: Enable working hours filtering (true/false)\n- JIRA_SLA_WORKING_HOURS_START: Start time (e.g., \"09:00\")\n- JIRA_SLA_WORKING_HOURS_END: End time (e.g., \"17:00\")\n- JIRA_SLA_WORKING_DAYS: Working days (e.g., \"1,2,3,4,5\" for Mon-Fri)\n- JIRA_SLA_TIMEZONE: Timezone for calculations (e.g., \"America/New_York\")","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issue_watchers","description":true,"schema":true,"before":"Get the list of watchers for a Jira issue.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n\nReturns:\n    JSON string with watcher count and list of watchers.\n\nRaises:\n    ValueError: If the Jira client is not configured or available.","after":"Get the list of watchers for a Jira issue.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issues_development_info","description":true,"schema":true,"before":"Get development information for multiple Jira issues.\n\nBatch retrieves development panel information (PRs, commits, branches)\nfor multiple issues at once.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_keys: List of Jira issue keys.\n    application_type: Optional filter by source control type.\n    data_type: Optional filter by data type.\n\nReturns:\n    JSON string with list of development information for each issue.","after":"Get development information for multiple Jira issues.\n\nBatch retrieves development panel information (PRs, commits, branches)\nfor multiple issues at once.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_link_types","description":true,"schema":true,"before":"Get all available issue link types.\n\nArgs:\n    ctx: The FastMCP context.\n    name_filter: Optional substring to filter link types by name.\n\nReturns:\n    JSON string representing a list of issue link type objects.","after":"Get all available issue link types.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_proforma_form_details","description":true,"schema":true,"before":"Get detailed information about a specific ProForma form.\n\nUses the new Jira Forms REST API. Returns form details including ADF design structure.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: The issue key containing the form.\n    form_id: The form UUID identifier.\n\nReturns:\n    JSON string representing the ProForma form details, or an error object if failed.","after":"Get detailed information about a specific ProForma form.\n\nUses the new Jira Forms REST API. Returns form details including ADF design structure.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_project_components","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_project_fields","description":true,"schema":true,"before":"Get the fields available on issues of a project (the create schema),\ndeduplicated across the project's issue types — i.e. which fields tickets in\nthis project have, regardless of whether they are filled.\n\nArgs:\n    ctx: The FastMCP context.\n    project_key: The project key.\n\nReturns:\n    JSON string with a list of fields: each {field_id, name, required,\n    schema_type, custom, issue_types}. Empty list if none / on error.\n\nRaises:\n    ValueError: If the Jira client is not configured or available.","after":"Get the fields available on issues of a project (the create schema),\ndeduplicated across the project's issue types — i.e. which fields tickets in\nthis project have, regardless of whether they are filled.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_project_issue_types","description":true,"schema":true,"before":"Get available issue types for a Jira project.\n\nReturns the list of issue types (Bug, Task, Story, Epic, etc.) that can\nbe created in the specified project. Use the returned issue type IDs with\nget_create_fields to discover what fields each type requires.\n\nArgs:\n    ctx: The FastMCP context.\n    project_key: The project key.\n\nReturns:\n    JSON string with list of issue types (id, name, description, subtask).","after":"Get available issue types for a Jira project.\n\nReturns the list of issue types (Bug, Task, Story, Epic, etc.) that can\nbe created in the specified project. Use the returned issue type IDs with\nget_create_fields to discover what fields each type requires.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_project_issues","description":true,"schema":true,"before":"Get all issues for a specific Jira project.\n\nArgs:\n    ctx: The FastMCP context.\n    project_key: The project key.\n    limit: Maximum number of results.\n    start_at: Starting index for pagination.\n\nReturns:\n    JSON string representing the search results including pagination info.","after":"Get all issues for a specific Jira project.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_project_versions","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_queue_issues","description":true,"schema":true,"before":"Get issues from a Jira Service Desk queue.\n\nServer/Data Center only. Not available on Jira Cloud.\n\nArgs:\n    ctx: The FastMCP context.\n    service_desk_id: Service desk ID.\n    queue_id: Queue ID.\n    start_at: Starting index for pagination.\n    limit: Maximum number of issues to return.\n\nReturns:\n    JSON string with queue metadata, issues, and pagination metadata.\n\nRaises:\n    NotImplementedError: If connected to Jira Cloud (Server/DC only).","after":"Get issues from a Jira Service Desk queue.\n\nServer/Data Center only. Not available on Jira Cloud.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_service_desk_for_project","description":true,"schema":true,"before":"Get the Jira Service Desk associated with a project key.\n\nServer/Data Center only. Not available on Jira Cloud.\n\nArgs:\n    ctx: The FastMCP context.\n    project_key: Jira project key.\n\nReturns:\n    JSON string with project key and service desk data (or null if not found).\n\nRaises:\n    NotImplementedError: If connected to Jira Cloud (Server/DC only).","after":"Get the Jira Service Desk associated with a project key.\n\nServer/Data Center only. Not available on Jira Cloud.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_service_desk_queues","description":true,"schema":true,"before":"Get queues for a Jira Service Desk.\n\nServer/Data Center only. Not available on Jira Cloud.\n\nArgs:\n    ctx: The FastMCP context.\n    service_desk_id: Service desk ID.\n    start_at: Starting index for pagination.\n    limit: Maximum number of queues to return.\n\nReturns:\n    JSON string with queue list and pagination metadata.\n\nRaises:\n    NotImplementedError: If connected to Jira Cloud (Server/DC only).","after":"Get queues for a Jira Service Desk.\n\nServer/Data Center only. Not available on Jira Cloud.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_sprint_issues","description":true,"schema":true,"before":"Get jira issues from sprint.\n\nArgs:\n    ctx: The FastMCP context.\n    sprint_id: The ID of the sprint.\n    fields: Comma-separated fields to return.\n    start_at: Starting index.\n    limit: Maximum results.\n\nReturns:\n    JSON string representing the search results including pagination info.","after":"Get jira issues from sprint.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_sprints_from_board","description":true,"schema":true,"before":"Get jira sprints from board by state.\n\nArgs:\n    ctx: The FastMCP context.\n    board_id: The ID of the board.\n    state: Sprint state ('active', 'future', 'closed'). If None, returns all sprints.\n    start_at: Starting index.\n    limit: Maximum results.\n\nReturns:\n    JSON string representing a list of sprint objects.","after":"Get jira sprints from board by state.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_transitions","description":true,"schema":true,"before":"Get available status transitions for a Jira issue.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n\nReturns:\n    JSON string representing a list of available transitions.","after":"Get available status transitions for a Jira issue.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_user_profile","description":true,"schema":true,"before":"Retrieve profile information for a specific Jira user.\n\nArgs:\n    ctx: The FastMCP context.\n    user_identifier: User identifier (email, username, key, or account ID).\n\nReturns:\n    JSON string representing the Jira user profile object, or an error object if not found.\n\nRaises:\n    ValueError: If the Jira client is not configured or available.","after":"Retrieve profile information for a specific Jira user.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_worklog","description":true,"schema":true,"before":"Get worklog entries for a Jira issue.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n\nReturns:\n    JSON string representing the worklog entries.","after":"Get worklog entries for a Jira issue.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_link_to_epic","description":true,"schema":true,"before":"Link an existing issue to an epic.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: The key of the issue to link.\n    epic_key: The key of the epic to link to.\n\nReturns:\n    JSON string representing the updated issue object.\n\nRaises:\n    ValueError: If in read-only mode or Jira client unavailable.","after":"Link an existing issue to an epic.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_move_issue","description":true,"schema":true,"before":"Move a Jira issue to a different project (Jira Cloud only).\n\nUses Jira Cloud's bulk move API to perform a cross-project move.\nThe issue keeps its current issue type and may be assigned a new key in the\ntarget project (e.g., OLDPROJ-123 becomes NEWPROJ-456).\n\nThe move is processed asynchronously on Jira's side; this tool polls\nuntil confirmed or times out after 30 seconds.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key of the issue to move.\n    target_project_key: Key of the target project.\n\nReturns:\n    JSON string representing the moved issue with its new key and project.\n\nRaises:\n    ValueError: If in read-only mode, Jira client unavailable, or the move fails.\n    NotImplementedError: If not running on Jira Cloud.","after":"Move a Jira issue to a different project (Jira Cloud only).\n\nUses Jira Cloud's bulk move API to perform a cross-project move.\nThe issue keeps its current issue type and may be assigned a new key in the\ntarget project (e.g., OLDPROJ-123 becomes NEWPROJ-456).\n\nThe move is processed asynchronously on Jira's side; this tool polls\nuntil confirmed or times out after 30 seconds.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_move_issues_to_backlog","description":true,"schema":true,"before":"Move issues to the backlog, removing them from any sprint.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_keys: Comma-separated issue keys.\n\nReturns:\n    JSON string with success message.\n\nRaises:\n    ValueError: If in read-only mode or Jira client unavailable.","after":"Move issues to the backlog, removing them from any sprint.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_remove_issue_link","description":true,"schema":true,"before":"Remove a link between two Jira issues.\n\nArgs:\n    ctx: The FastMCP context.\n    link_id: The ID of the link to remove.\n\nReturns:\n    JSON string indicating success.\n\nRaises:\n    ValueError: If link_id is missing, in read-only mode, or Jira client unavailable.","after":"Remove a link between two Jira issues.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_remove_watcher","description":true,"schema":true,"before":"Remove a user from watching a Jira issue.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n    username: Username to remove (Server/DC).\n    account_id: Account ID to remove (Cloud).\n\nReturns:\n    JSON string with success confirmation.\n\nRaises:\n    ValueError: If the Jira client is not configured or available.","after":"Remove a user from watching a Jira issue.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_search","description":true,"schema":true,"before":"Search Jira issues using JQL (Jira Query Language).\n\nArgs:\n    ctx: The FastMCP context.\n    jql: JQL query string.\n    fields: Comma-separated fields to return.\n    limit: Maximum number of results.\n    start_at: Starting index for pagination.\n    projects_filter: Comma-separated list of project keys to filter by.\n    expand: Optional fields to expand.\n    page_token: Pagination token from a previous search result (Cloud only).\n\nReturns:\n    JSON string representing the search results including pagination info.","after":"Search Jira issues using JQL (Jira Query Language).","propsAdded":["use_display_names"],"propsRemoved":[]},{"tool":"jira_search_assignable_users","description":true,"schema":true,"before":"Search Jira users assignable in a given project or issue.\n\nUse this when you have a display name / partial name / email fragment\nand need a concrete identifier (``name`` / ``key`` for Server/DC,\n``accountId`` for Cloud) to feed into assignee, reporter, watcher, etc.\n\nReturns the full result set so the caller can disambiguate when several\nusers match — ``get_user_profile`` only resolves one identifier and is\nnot designed for human-name search.\n\nExactly one of ``project_key`` or ``issue_key`` must be provided — the\nunderlying API (``/user/assignable/search``) requires a project or issue\ncontext and works without the global \"Browse Users\" permission that bot\naccounts in locked-down DC instances often lack.\n\nArgs:\n    ctx: The FastMCP context.\n    query: Display name / username / email substring.\n    project_key: Project key (e.g. 'DT') to scope the search.\n    issue_key: Issue key (e.g. 'DT-779') to scope the search.\n    limit: Maximum number of users to return.\n\nReturns:\n    JSON string: {\"success\": true, \"count\": N, \"users\": [...]} on success,\n    or an error object on failure.","after":"Search Jira users assignable in a given project or issue.\n\nUse this when you have a display name / partial name / email fragment\nand need a concrete identifier (``name`` / ``key`` for Server/DC,\n``accountId`` for Cloud) to feed into assignee, reporter, watcher, etc.\n\nReturns the full result set so the caller can disambiguate when several\nusers match — ``get_user_profile`` only resolves one identifier and is\nnot designed for human-name search.\n\nExactly one of ``project_key`` or ``issue_key`` must be provided — the\nunderlying API (``/user/assignable/search``) requires a project or issue\ncontext and works without the global \"Browse Users\" permission that bot\naccounts in locked-down DC instances often lack.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_search_fields","description":true,"schema":true,"before":"Search Jira fields by keyword with fuzzy match.\n\nArgs:\n    ctx: The FastMCP context.\n    keyword: Keyword for fuzzy search.\n    limit: Maximum number of results.\n    refresh: Whether to force refresh the field list.\n\nReturns:\n    JSON string representing a list of matching field definitions.","after":"Search Jira fields by keyword with fuzzy match.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_search_projects","description":true,"schema":true,"before":"Search for Jira projects by name or key prefix.\n\nUses the projects picker endpoint to return a ranked list of matching\nprojects without fetching every visible project on the instance.\n\nArgs:\n    ctx: The FastMCP context.\n    query: Name or key prefix to search for.\n    max_results: Maximum number of results to return.\n    current_project_ids: Comma-separated project IDs to exclude.\n\nReturns:\n    JSON string representing a list of matching project objects.\n    Project keys are always returned in uppercase.\n    If JIRA_PROJECTS_FILTER is configured, only returns projects matching those keys.","after":"Search for Jira projects by name or key prefix.\n\nUses the projects picker endpoint to return a ranked list of matching\nprojects without fetching every visible project on the instance.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_transition_issue","description":true,"schema":true,"before":"Transition a Jira issue to a new status.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n    transition_id: ID of the transition.\n    fields: Optional JSON string of fields to update during transition.\n    comment: Optional comment for the transition in Markdown format.\n\nReturns:\n    JSON string representing the updated issue object.\n\nRaises:\n    ValueError: If required fields missing, invalid input, in read-only mode, or Jira client unavailable.","after":"Transition a Jira issue to a new status.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_update_issue","description":true,"schema":true,"before":"Update an existing Jira issue including changing status, adding Epic links, updating fields, etc.\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: Jira issue key.\n    fields: JSON string of fields to update. Text fields like 'description' should use Markdown format.\n    additional_fields: Optional JSON string of additional fields.\n    components: Comma-separated list of component names.\n    attachments: Optional JSON array string or comma-separated list of file paths.\n\nReturns:\n    JSON string representing the updated issue object and attachment results.\n\nRaises:\n    ValueError: If in read-only mode or Jira client unavailable, or invalid input.","after":"Update an existing Jira issue including changing status, adding Epic links, updating fields, etc.","propsAdded":["return_fields"],"propsRemoved":[]},{"tool":"jira_update_proforma_form_answers","description":true,"schema":true,"before":"Update form field answers using the Jira Forms REST API.\n\nThis is the primary method for updating form data. Each answer object\nmust specify the question ID, answer type, and value.\n\n**⚠️ KNOWN LIMITATION - DATETIME fields:**\nThe Jira Forms API does NOT properly preserve time components in DATETIME fields.\nOnly the date portion is stored; times are reset to midnight (00:00:00).\n\n**Workaround for DATETIME fields:**\nUse jira_update_issue to directly update the underlying custom fields instead:\n1. Get the custom field ID from the form details (question's \"jiraField\" property)\n2. Use jira_update_issue with fields like: {\"customfield_XXXXX\": \"2026-01-09T11:50:00-08:00\"}\n\nExample:\n```python\n# Instead of updating via form (loses time):\n# jira_update_proforma_form_answers(issue_key, form_id, [{\"questionId\": \"91\", \"type\": \"DATETIME\", \"value\": \"...\"}])\n\n# Use direct field update (preserves time):\njira_update_issue(issue_key, {\"customfield_10542\": \"2026-01-09T11:50:00-08:00\"})\n```\n\n**Automatic DateTime Conversion:**\nFor DATE and DATETIME fields, you can provide values as:\n- ISO 8601 strings (e.g., \"2024-12-17T19:00:00Z\", \"2024-12-17\")\n- Unix timestamps in milliseconds (e.g., 1734465600000)\n\nThe tool automatically converts ISO 8601 strings to Unix timestamps.\n\nExample answers:\n[\n    {\"questionId\": \"q1\", \"type\": \"TEXT\", \"value\": \"Updated description\"},\n    {\"questionId\": \"q2\", \"type\": \"SELECT\", \"value\": \"Product A\"},\n    {\"questionId\": \"q3\", \"type\": \"NUMBER\", \"value\": 42},\n    {\"questionId\": \"q4\", \"type\": \"DATE\", \"value\": \"2024-12-17\"}\n]\n\nCommon answer types:\n- TEXT: String values\n- NUMBER: Numeric values\n- DATE: Date values (ISO 8601 string or Unix timestamp in ms)\n- DATETIME: DateTime values - ⚠️ USE WORKAROUND ABOVE\n- SELECT: Single selection from options\n- MULTI_SELECT: Multiple selections (value as list)\n- CHECKBOX: Boolean values\n\nArgs:\n    ctx: The FastMCP context.\n    issue_key: The issue key containing the form.\n    form_id: The form UUID (get from get_issue_proforma_forms).\n    answers: List of answer objects with questionId, type, and value.\n\nReturns:\n    JSON string with operation result.","after":"Update form field answers using the Jira Forms REST API.\n\nThis is the primary method for updating form data. Each answer object\nmust specify the question ID, answer type, and value.\n\n**⚠️ KNOWN LIMITATION - DATETIME fields:**\nThe Jira Forms API does NOT properly preserve time components in DATETIME fields.\nOnly the date portion is stored; times are reset to midnight (00:00:00).\n\n**Workaround for DATETIME fields:**\nUse jira_update_issue to directly update the underlying custom fields instead:\n1. Get the custom field ID from the form details (question's \"jiraField\" property)\n2. Use jira_update_issue with fields like: {\"customfield_XXXXX\": \"2026-01-09T11:50:00-08:00\"}\n\nExample:\n```python\n# Instead of updating via form (loses time):\n# jira_update_proforma_form_answers(issue_key, form_id, [{\"questionId\": \"91\", \"type\": \"DATETIME\", \"value\": \"...\"}])\n\n# Use direct field update (preserves time):\njira_update_issue(issue_key, {\"customfield_10542\": \"2026-01-09T11:50:00-08:00\"})\n```\n\n**Automatic DateTime Conversion:**\nFor DATE and DATETIME fields, you can provide values as:\n- ISO 8601 strings (e.g., \"2024-12-17T19:00:00Z\", \"2024-12-17\")\n- Unix timestamps in milliseconds (e.g., 1734465600000)\n\nThe tool automatically converts ISO 8601 strings to Unix timestamps.\n\nExample answers:\n[\n    {\"questionId\": \"q1\", \"type\": \"TEXT\", \"value\": \"Updated description\"},\n    {\"questionId\": \"q2\", \"type\": \"SELECT\", \"value\": \"Product A\"},\n    {\"questionId\": \"q3\", \"type\": \"NUMBER\", \"value\": 42},\n    {\"questionId\": \"q4\", \"type\": \"DATE\", \"value\": \"2024-12-17\"}\n]\n\nCommon answer types:\n- TEXT: String values\n- NUMBER: Numeric values\n- DATE: Date values (ISO 8601 string or Unix timestamp in ms)\n- DATETIME: DateTime values - ⚠️ USE WORKAROUND ABOVE\n- SELECT: Single selection from options\n- MULTI_SELECT: Multiple selections (value as list)\n- CHECKBOX: Boolean values","propsAdded":[],"propsRemoved":[]},{"tool":"jira_update_sprint","description":true,"schema":true,"before":"Update jira sprint.\n\nArgs:\n    ctx: The FastMCP context.\n    sprint_id: The ID of the sprint.\n    name: Optional new name.\n    state: Optional new state (future|active|closed).\n    start_date: Optional new start date.\n    end_date: Optional new end date.\n    goal: Optional new goal.\n\nReturns:\n    JSON string representing the updated sprint object or an error message.\n\nRaises:\n    ValueError: If in read-only mode or Jira client unavailable.","after":"Update jira sprint.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_update_version","description":true,"schema":true,"before":"Update an existing fix version in a Jira project.\n\nOnly fields explicitly provided are modified; other attributes of the\nversion are left untouched. Useful for archiving/unarchiving versions,\nrenaming, or shifting release dates without recreating them.\n\nArgs:\n    ctx: The FastMCP context.\n    version_id: Numeric ID of the version to update.\n    name: New name (optional).\n    description: New description (optional).\n    start_date: New start date YYYY-MM-DD (optional).\n    release_date: New release date YYYY-MM-DD (optional).\n    archived: Archived flag (optional).\n    released: Released flag (optional).\n\nReturns:\n    JSON string of the updated version object.","after":"Update an existing fix version in a Jira project.\n\nOnly fields explicitly provided are modified; other attributes of the\nversion are left untouched. Useful for archiving/unarchiving versions,\nrenaming, or shifting release dates without recreating them.","propsAdded":[],"propsRemoved":[]}]},{"from":"0.23.0","to":"0.23.1","published":"2026-08-19","bump":"patch","added":[],"removed":[],"changed":[{"tool":"jira_get_board_issues","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issue","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_sprint_issues","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_search","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]}]},{"from":"0.23.1","to":"0.24.0","published":"2026-11-08","bump":"minor","added":[],"removed":[],"changed":[{"tool":"jira_add_comment","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_assign_issue","description":true,"schema":true,"before":"Assign a Jira issue to a user using the dedicated assignment endpoint.\n\nThis is more reliable than setting assignee via update_issue, which is\nsilently ignored by some Jira configurations. Uses PUT /issue/{key}/assignee.","after":"Assign a Jira issue to a user using the dedicated assignment endpoint.\n\nThis is more reliable than setting assignee via update_issue, which is\nsilently ignored by some Jira configurations. Uses PUT /issue/{key}/assignee.\n\nOn Jira Server/DC the following identifier forms are all accepted:\nlogin name, email address, display name, or JIRAUSER key. The resolution\norder is: key lookup → email search (with email-as-username fallback) →\ntext search → assignable-user search scoped to the issue.","propsAdded":[],"propsRemoved":[]},{"tool":"jira_create_issue","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_board_issues","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_issue","description":true,"schema":true,"before":"Get details of a specific Jira issue.\n\nIncludes Epic links and relationship information. Use the\n``include`` parameter to inline enrichments (remote_links,\ntransitions, watchers, changelog, comments, worklogs) so that\nseparate tool calls are not needed.","after":"Get details of a specific Jira issue.\n\nIncludes Epic links and relationship information. Use the\n``include`` parameter to inline enrichments (remote_links,\ntransitions, watchers, changelog, comments, worklogs, epic_summary)\nso that separate tool calls are not needed. The ``epic_summary``\nsection only applies when the issue is an Epic and adds child-issue\naggregations (counts by status, assignee, and type, plus a\ncompletion percentage); it is aggregate-only unless\n``epic_summary_children`` is set.","propsAdded":["epic_summary_children","max_epic_children"],"propsRemoved":[]},{"tool":"jira_get_sprint_issues","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_user_profile","description":true,"schema":true,"before":"Retrieve profile information for a specific Jira user.","after":"Retrieve profile information for a Jira user.\n\nUse ``user_identifier=\"me\"`` to return the account authenticated for the\ncurrent request directly from Jira's ``/myself`` endpoint. This path does\nnot require Browse Users permission.","propsAdded":["expand"],"propsRemoved":[]},{"tool":"jira_search","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_transition_issue","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_update_issue","description":true,"schema":true,"before":"Update an existing Jira issue including changing status, adding Epic links, updating fields, etc.","after":"Update an issue and optionally transition, comment, and log work.","propsAdded":["attachments_base64","comment","comment_visibility","transition","worklog","worklog_started"],"propsRemoved":[]}]},{"from":"0.24.0","to":"0.24.1","published":"2026-11-08","bump":"patch","added":[],"removed":[],"changed":[{"tool":"jira_remove_issue_link","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]}]},{"from":"0.24.1","to":"0.24.2","published":"2026-11-12","bump":"patch","added":[],"removed":[],"changed":[{"tool":"jira_get_issue","description":false,"schema":true,"propsAdded":[],"propsRemoved":[]},{"tool":"jira_get_transitions","description":false,"schema":true,"propsAdded":["expand_fields"],"propsRemoved":[]},{"tool":"jira_transition_issue","description":false,"schema":true,"propsAdded":["update_data"],"propsRemoved":[]}]},{"from":"0.24.2","to":"0.24.3","published":"2026-11-12","bump":"patch","added":[],"removed":[],"changed":[]}]}}