Skip to content

Control 1.2.4

Latest

Choose a tag to compare

@Italia1235 Italia1235 released this 17 Nov 10:16

Установка / Installation

Скачайте control-1.2.4.jar и установите через Jira → Administration → Manage apps → Upload app.

Jira 10.3.x, Java 17. Перед обновлением дождитесь завершения операций; после установки переподключите MCP-клиент.

Built with mvn -B -ntp clean package; packaged JAR checked with PluginPackagingTest. Not smoke-tested on a running Jira in this release session.

SHA-256 (control-1.2.4.jar):

f8a95b58eecb6270a662cb6a9632fc468a4d65a4301cf6f3bcebce2ef99d2d14

1.2.4 — 2026-11-15

Includes the changes of 1.2.3 (2026-11-13).

Screen schemes

  • New set_issue_type_screen_scheme_mappings: edits the rows (issue type → Screen Scheme) of an existing Issue Type Screen Scheme in place, for every project that uses it. Rows are ADD / REPLACE / REMOVE; adding a row that already exists is treated as a replace with an ADD_AS_REPLACE warning.
  • New set_screen_scheme_operations: edits the rows (operation → screen) of an existing Screen Scheme in place, for every Issue Type Screen Scheme and project that uses it.
  • New assign_issue_type_screen_scheme: switches one project to an existing Issue Type Screen Scheme (or back to the default one). Only the project link changes; schemes and screens are neither edited nor copied, and issues are not migrated.
  • The previews of all three tools show the effective CREATE/EDIT/VIEW screens before → after per issue type, how many projects are linked and how many actually change, and warnings for an orphaned or shared scheme and for required fields missing from the new create screen.
  • The outcome is read back from Jira: CHANGED only when Jira matches the plan, otherwise PARTIALLY_CHANGED, FAILED or UNKNOWN. These tools are forward-only: there is no rollback.

Projects

  • create_project creates Business projects (Project Management, Task Management, Process Management) and Software projects (Scrum, Kanban, Basic) from supported templates. action:"list_templates" reads the template catalog; action:"create" requires a templateKey. Jira Service Management and third-party templates are not supported.
  • Breaking: the old create_project request without action/templateKey is rejected.
  • Rollback of a Software project created through Control is refused: its board and filter are not tracked by Control.
  • Software templates have only been verified by unit tests, not on a live Jira.

Workflows

  • Breaking: edit_workflow is removed without an alias. Its structural edits now go to configure_workflow under existing.changes, in the same plan as screens and rules: rename and add transitions, change sources, targets and resolution, add and remove steps.
  • New statuses can be added to an existing workflow by name and category (ADD_STATUS.newStatus); a status with the same name is reused, an ambiguous name is refused.

Fields

  • get_field_contexts accepts an optional project and returns the global contexts plus the contexts that include that project.

Fixes

  • A failed read of option defaults while changing options is no longer masked as an empty set.
  • Matching an existing workflow graph now takes the transition view into account, not only screen metadata.
  • Cancelling configure_workflow between native steps returns CANCELLED instead of JIRA_ERROR.

Security

  • Breaking: every /rest/control/1.0/changes/* endpoint now requires Authorization: Bearer <PAT> and rejects a foreign Origin, like /mcp. Requests with only a session cookie or Basic auth get 401, a foreign Origin gets 403.

Полная история / Full history: https://github.com/Italia1235/control/blob/v1.2.4/Versions.md