<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
  <id>https://oktul.com/feed.xml</id>
  <title>Oktul release notes</title>
  <subtitle>Each release of an Oktul app for Atlassian Cloud, newest first, dated by the day it reached the Atlassian Marketplace.</subtitle>
  <link rel="self" type="application/atom+xml" href="https://oktul.com/feed.xml"/>
  <link rel="alternate" type="text/html" href="https://oktul.com/"/>
  <updated>2026-10-02T00:00:00Z</updated>
  <author><name>Oktul</name><uri>https://oktul.com/</uri></author>
  <icon>https://oktul.com/images/logo/oktul-app-icon-192.png</icon>
  <logo>https://oktul.com/images/logo/oktul-logo-light-512.png</logo>
  <entry>
    <id>tag:oktul.com,2026:work-item-selector/3.7.0</id>
    <title>Oktul Work Item Selector for Jira 3.7.0</title>
    <link rel="alternate" type="text/html" href="https://oktul.com/docs/plugins/work-item-selector/release-notes/#370-october-2026"/>
    <link rel="alternate" type="text/markdown" href="https://oktul.com/docs/plugins/work-item-selector/release-notes/index.md"/>
    <published>2026-10-02T00:00:00Z</published>
    <updated>2026-10-02T00:00:00Z</updated>
    <category term="work-item-selector" label="Oktul Work Item Selector for Jira"/>
    <summary>Dependency security updates, no change in behaviour</summary>
    <content type="text">Security updates to four third-party packages. The app behaves exactly as before.

The updated packages are fast-uri, undici, markdown-it and brace-expansion,
which between them carried 17 published advisories, the most serious rated high:
host confusion in URI parsing, and denial of service in WebSocket decompression.

None of the four runs inside the app. They arrive through Atlassian's Forge packages,
which reference them for type definitions only, and through the lint tools that check
the app's source code. The code deployed to your site and the workflow validator's configuration screen contain
none of them. They were updated anyway, so that a dependency audit of this release
reports nothing.

It adds no scope and no external permission, so upgrading needs no approval from an
administrator and no data leaves Atlassian.</content>
  </entry>
  <entry>
    <id>tag:oktul.com,2026:work-item-selector/3.6.0</id>
    <title>Oktul Work Item Selector for Jira 3.6.0</title>
    <link rel="alternate" type="text/html" href="https://oktul.com/docs/plugins/work-item-selector/release-notes/#360-september-2026"/>
    <link rel="alternate" type="text/markdown" href="https://oktul.com/docs/plugins/work-item-selector/release-notes/index.md"/>
    <published>2026-09-25T00:00:00Z</published>
    <updated>2026-09-25T00:00:00Z</updated>
    <category term="work-item-selector" label="Oktul Work Item Selector for Jira"/>
    <summary>No Load more button, picker columns cut to 40 characters</summary>
    <content type="text">The picker is shorter: no Load more button, and each column cut to 40 characters.

- The Load more work items button is gone. The picker opens on the first 25 work
  items in scope, and typing narrows the list. The button paged through the rest of the
  scope 25 at a time.
- Each column in a picker option is cut to 40 characters, spaces included, and ends
  in an ellipsis where it was cut. A long summary or description used to stretch the
  edit box. The cards on the work item are unchanged.

It adds no scope and no external permission, so upgrading needs no approval from an
administrator and no data leaves Atlassian.</content>
  </entry>
  <entry>
    <id>tag:oktul.com,2026:work-item-selector/3.5.0</id>
    <title>Oktul Work Item Selector for Jira 3.5.0</title>
    <link rel="alternate" type="text/html" href="https://oktul.com/docs/plugins/work-item-selector/release-notes/#350-september-2026"/>
    <link rel="alternate" type="text/markdown" href="https://oktul.com/docs/plugins/work-item-selector/release-notes/index.md"/>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <category term="work-item-selector" label="Oktul Work Item Selector for Jira"/>
    <summary>Estonian translation and editing fixes</summary>
    <content type="text">The app follows each person's Atlassian profile language, in English or Estonian.

Every screen is translated: the picker, the issue view, the field configuration screen
and its knowledge base, the Automation action's form and the workflow validator's
configuration. So are the field type names and descriptions Jira lists, and the message
Jira shows when a typed value is rejected. Any other profile language shows English.

Three kinds of text stay in English: error messages from the app's backend, messages in
the Automation audit log, and the workflow validator's default block messages. An
administrator can replace each block message with their own wording, in any language.

- Field settings open one section at a time. Work item scope opens first, and
  opening another section closes the one that was open. The knowledge base and the help
  card stay open.
- Save checks the configuration instead of staying disabled. An invalid scope used
  to disable it, and with the sections folded away the reason could be out of sight.
  Save now checks the scope again, and a rejected scope, column set or link type opens
  the section it concerns.
- The cursor stays where you put it. Editing the middle of the JQL scope, the
  picker's placeholder text, the Automation action's work items or a validator message
  moved the cursor to the end after every keystroke.
- The JQL scope box no longer takes focus by itself.
- Clear keeps the work items box on screen. With Clear the selection chosen, the
  Automation action hid the box while the keys still in it stopped the rule from
  running. The box now stays visible until it is empty.
- Shorter wording throughout the app, with one term per concept: work item in
  English, pilet in Estonian.

It adds no scope and no external permission, so upgrading needs no approval from an
administrator and no data leaves Atlassian.</content>
  </entry>
  <entry>
    <id>tag:oktul.com,2026:work-item-selector/3.4.0</id>
    <title>Oktul Work Item Selector for Jira 3.4.0</title>
    <link rel="alternate" type="text/html" href="https://oktul.com/docs/plugins/work-item-selector/release-notes/#340-september-2026"/>
    <link rel="alternate" type="text/markdown" href="https://oktul.com/docs/plugins/work-item-selector/release-notes/index.md"/>
    <published>2026-09-21T00:00:00Z</published>
    <updated>2026-09-21T00:00:00Z</updated>
    <category term="work-item-selector" label="Oktul Work Item Selector for Jira"/>
    <summary>Initial public release</summary>
    <content type="text">First release: work item picker custom fields, scoped by JQL per field context.

Two custom field types, Oktul Work Item Selector (Single Select) and Oktul Work Item Selector (Multi select),
holding up to 100 work items, the Forge platform limit.

- JQL scope per field context, validated live as it is typed. Placeholders read the
  current work item and user, so one configuration behaves differently on every work
  item: parent = {{issue.key}}, assignee = {{user.accountId}}.
- Permission mode: search as the viewer, or as the app.
- One to seven columns on each card, drawn the way Jira draws them.
- Four JQL functions and eight aliases covering both directions of a relationship,
  plus Automation smart values and JQL autocomplete.
- A &quot;Set work item selection&quot; Automation action: replace, add to, remove from, clear.
- A workflow validator: require a selection, require statuses, restrict projects,
  prevent circular dependencies.
- Optional native Jira issue links, created and removed with the selection.

No data leaves Atlassian. The app declares no external permissions.

The version here is the Marketplace version, which is what you compare against the
version installed on your site. It runs independently of the source repository's own
numbering.</content>
  </entry>
</feed>
