# Oktul > Atlassian Cloud apps built by Atlassian architects. Oktul is an Estonian Atlassian Marketplace Partner company of highly certified and experienced solution architects. We build Jira, Confluence and other Atlassian apps that run inside your own Atlassian Cloud. Atlassian's Teamwork Graph makes their data available to the AI agents you connect. ## What sets Oktul apart - Built by Atlassian solution architects: 14,000+ hours implementing the Atlassian platform, 7+ years each of experience as architects, 23 Atlassian certifications and accreditations. The company page lists each designation and certification with the month it was awarded: https://oktul.com/about/ - Security and privacy decided by the platform: every application runs on Atlassian Forge inside the customer's own Atlassian site, so no part of Oktul's infrastructure sits between users and their work. Each application's privacy notice names every host it may contact. CSA STAR Level 1 self-assessments are published for the company and every application, and ISO/IEC 27001 certification is expected by March 2027 at the latest: https://oktul.com/trust/ - AI-ready context: the applications keep work and its context in Jira and Confluence, where Atlassian's Teamwork Graph, Rovo and other agentic teammates read it with each person's permissions. None runs an AI model of its own: https://oktul.com/apps/ - What it builds: Marketplace applications for Jira and Confluence Cloud, and custom Atlassian Cloud applications on Forge for one organisation's process: https://oktul.com/custom-development/ ## Company facts - Registered name: Oktul OÜ, registry code 17589681 (https://ariregister.rik.ee/eng/company/17589681/OKTUL-O%C3%9C) - Founded: 2026, Tallinn, Harjumaa, Estonia - Atlassian Marketplace Partner: https://marketplace.atlassian.com/vendors/534484195 - LinkedIn: https://www.linkedin.com/company/oktul - YouTube: https://www.youtube.com/@OktulDevelopment - Kevin Kadakas, Co-founder & Solution Architect: https://www.linkedin.com/in/kadakaskevin - Jürgen Talik, Co-founder & Solution Architect: https://www.linkedin.com/in/jurgen-talik - Support: first response within 24 hours, Monday to Friday, through the Help Center or support@oktul.com - Legal notices and data protection requests: legal@oktul.com - Everything else: hello@oktul.com Oktul is listed in the CSA STAR Registry at Level 1, with the CAIQ Lite questionnaire it completed and published for the company: https://cloudsecurityalliance.org/star/registry/oktul-ou/services/oktul-ou. Every page below is also served as markdown at the URL shown. Those files are generated from the same content as the HTML, so they cannot disagree with it. ## Start here - [Atlassian Cloud apps built by Atlassian architects](https://oktul.com/index.md): what Oktul builds and for whom, the applications you can install today, how they feed Atlassian's Teamwork Graph for Rovo and other agents, and the questions a security review asks first. - [Trust and data handling](https://oktul.com/trust/index.md): where the applications run, what data leaves an Atlassian site and why, the support commitment with a resolution target for each priority, how to report a vulnerability, and what our research into Rovo, the Teamwork Graph and outside AI assistants such as Claude decided for each application. Read this page for a security or procurement question. - [About us](https://oktul.com/about/index.md): who builds the applications and why that matters to a buyer, the four problems Oktul's applications solve, their Atlassian designations and certifications with the month each was awarded, how every release is tested, and the company's registration details. - [Jira and Confluence apps on Atlassian Forge](https://oktul.com/apps/index.md): every Oktul application, listed on the Atlassian Marketplace or awaiting Atlassian's approval, and how each keeps AI context on your Atlassian site, readable by the Teamwork Graph under Jira and Confluence permissions. - [Contact and support](https://oktul.com/contact/index.md): the Help Center, what can be raised there, and the three published email addresses and what each is for. - [Partner programme for Atlassian consultancies](https://oktul.com/partners/index.md): the partner programme for Atlassian consultancies, which is in development, what it will give a partner, and how to register interest early. - [Custom Atlassian app development](https://oktul.com/custom-development/index.md): custom Atlassian Cloud applications Oktul builds on Forge for one organisation's process, in Jira, Confluence, Bitbucket, Compass and Rovo: the steps from the first meeting to the release, when the rough and the accurate price come, who owns the application, how every application is built, and the questions buyers ask. The page also estimates a price range from the reader's answers. ## Applications - [Oktul Code Studio](https://oktul.com/apps/code-studio/index.md): Write, store and run JavaScript and TypeScript scripts in Jira and Confluence Cloud. Host: Jira Cloud and Confluence Cloud. - Documentation: https://oktul.com/docs/plugins/code-studio/ - Writing scripts for it: [what each trigger hands a script, Jira, Assets, the sandbox and long runs](https://oktul.com/docs/plugins/code-studio/writing-scripts/index.md), [requests to other APIs with get, post, put, patch and delete](https://oktul.com/docs/plugins/code-studio/requests-to-other-systems/index.md), [the API as TypeScript declarations](https://oktul.com/docs/plugins/code-studio/script-api/index.md), [whole scripts to adapt](https://oktul.com/docs/plugins/code-studio/script-examples/index.md), [snippets, one page per kind of script](https://oktul.com/docs/plugins/code-studio/snippets/starting-points/index.md) - Video: [Oktul Code Studio](https://oktul.com/videos/code-studio/), 38 seconds, no sound - Status: submitted to Atlassian. The Marketplace listing awaits approval, so it cannot be installed yet. - Price (Marketplace, 21.10.2026): USD 1.85 per user per month for 11–100 users, free up to 10 users. Costs less than ScriptRunner for Jira at every size up to 10,000 users. Costs less than ScriptRunner for Confluence at every size up to 10,000 users. Costs less than Power Scripts at every size up to 10,000 users. Costs less than Jira Misc Workflow Extensions (JMWE) at every size up to 10,000 users. One installation covers Jira and Confluence. ScriptRunner sells a Jira app and a Confluence app, so a site that scripts both pays for both, which the last row adds up. Scripts are JavaScript or TypeScript and run on Atlassian Forge inside the site, and the sandbox lists every write before anyone publishes a script. - Questions it answers: - **Should I install Code Studio for Jira or for Confluence?** The one for your site's main product, and only that one. Both listings are the same app with the same features, so a site with only Jira or only Confluence can install it. Connect the other product to the same installation. Two installations would be two separate Code Studios with no shared scripts. - **Can Rovo write a Jira script from a description?** Yes. Choose Script with Rovo, then Write a new script, and describe what it should do, or hand it exported Jira automation rules. The Rovo author plans the script, writes it as a draft and runs it in the sandbox. You see what it would change before anyone publishes it. It uses your organisation's Rovo AI credits. - **Can Code Studio run my ScriptRunner for Jira Cloud Groovy scripts?** Not as Groovy. Code Studio runs JavaScript and TypeScript. Its Rovo translator converts a Groovy script to a TypeScript draft beside the original and maps ScriptRunner's HAPI calls to the REST calls they make. It checks the draft and runs it in the sandbox, and a person publishes it. A fragment that is not a whole script is reported as not convertible. ScriptRunner Connect scripts run unchanged. - **How do I test a Jira script without changing anything?** Run it in Code Studio's sandbox. The script reads your site's real data, and every write it makes is recorded and answered with a simulated response instead of being sent. The run lists each change it would have made. Production runs only scripts a site administrator has published. - Privacy notice: https://oktul.com/docs/plugins/code-studio/privacy/ - Sends data outside Atlassian, to: Your repository provider: GitHub, Bitbucket Cloud, GitLab or another Git host you connect; Hosts your administrator approves. What each receives and keeps is in the privacy notice. - CSA STAR Registry, Level 1: a completed CAIQ Lite v4.1.0 self-assessment, all 138 questions, published by the Cloud Security Alliance. A self-assessment rather than an audit, and not every answer is yes: https://cloudsecurityalliance.org/star/registry/oktul-ou/services/oktul-code-studio - [Oktul Work Item Selector for Jira](https://oktul.com/apps/work-item-selector/index.md): Allow users to pick work items based on Jira Query Language (JQL). Host: Jira Cloud. - Documentation: https://oktul.com/docs/plugins/work-item-selector/ - Video: [Oktul Work Item Selector for Jira](https://oktul.com/videos/work-item-selector/), 29 seconds, no sound - Marketplace listing: https://marketplace.atlassian.com/3124527557 - Price (Marketplace, 21.10.2026): USD 0.30 per user per month for 11–100 users, free up to 10 users. Costs less than Issue Picker for Jira at every size up to 10,000 users. Costs more than Work Item Picker - Custom Issue Picker Field for Jira below 7,500 users, and less from 7,500. Costs less than Teamworkx Issue Picker for Jira at every size up to 10,000 users. The Starware's picker costs less on smaller sites, and it has no permission modes, no Automation action, no workflow validation, no JQL functions, no synced Jira links and no reverse lookups, which the comparison table sets out row by row. - Questions it answers: - **Can Rovo see which Jira work items are related?** Yes. Oktul Work Item Selector for Jira writes each relationship to a work item property on both work items and indexes it. Atlassian's Teamwork Graph reads work item properties, and Rovo and other agentic teammates find the relationships there without a native Jira link. JQL, the app's JQL functions such as workItemsSelectedBy, and Jira's REST API read them too. You can also keep each selection as a native Jira link, set per field context. - **How do I limit a Jira work item picker to the results of a JQL query?** Add a custom field whose search scope is a JQL query. Jira’s own work item link offers every work item the user can read on the site. Oktul Work Item Selector for Jira is such a field: an administrator sets the JQL on each field context, and the field offers only what it returns. With placeholders such as {{issue.key}} and {{user.accountId}}, the scope follows the work item and the person editing it. Elsewhere, such as bulk edit, the field is a plain text box. - Privacy notice: https://oktul.com/docs/plugins/work-item-selector/privacy/ - Runs on Atlassian: granted by Atlassian, per application, to apps that store data only on Atlassian's infrastructure and declare no external hosts. Not a company-wide claim: https://developer.atlassian.com/platform/marketplace/runs-on-atlassian/ - CSA STAR Registry, Level 1: a completed CAIQ Lite v4.1.0 self-assessment, all 138 questions, published by the Cloud Security Alliance. A self-assessment rather than an audit, and not every answer is yes: https://cloudsecurityalliance.org/star/registry/oktul-ou/services/oktul-work-item-selector-for-jira - [Oktul SignPlus for Confluence](https://oktul.com/apps/signplus/index.md): Sign a Confluence page, and prove later which version was signed. Host: Confluence Cloud. - Documentation: https://oktul.com/docs/plugins/signplus/ - Video: [SignPlus for Confluence](https://oktul.com/videos/signplus/), 35 seconds, no sound - Marketplace listing: https://marketplace.atlassian.com/1166020382 - Price (Marketplace, 21.10.2026): USD 0.70 per user per month for 11–100 users, free up to 10 users. Costs more than Digital Signature for Confluence below 5,000 users, and less from 5,000. Costs less than eSign Signatures for Confluence at every size up to 10,000 users. Costs more than Signature for Confluence at every size up to 10,000 users. The apps that cost less record a signature inside Confluence. SignPlus sends the page to Dokobit, and a signature made there with a qualified eID such as Smart-ID or an ID card is a qualified electronic signature, which eIDAS gives the legal effect of a handwritten one. Dokobit bills each signing on top, under the customer's own contract with Dokobit. - Questions it answers: - **Can you sign a Confluence page?** Not with Confluence alone: Confluence Cloud has no built-in way to sign a page. SignPlus adds one. Sign this page, under the page title, sends the page to Dokobit as a PDF or a signature container, each person signs with their own eID, and the signed document is attached back to the page. If the page is edited afterwards, the byline says Page signed but modified. - **How do I sign a Confluence page officially, so the signature is legally binding?** Start the signing from the page with SignPlus, and have each signer sign on Dokobit with a qualified eID. Signed with a qualified eID, such as Smart-ID or an Estonian, Latvian, Lithuanian, Finnish or Belgian ID card, it is a qualified electronic signature, which Article 25(2) of eIDAS gives the legal effect of a handwritten signature in every EU member state. Dokobit's list of eIDs on dokobit.com says which methods produce one. E-signature levels is QES only by default, which refuses the rest. A signing in test mode has no legal effect. - **Can a signed or exported Confluence page follow our corporate visual identity?** Yes, the document SignPlus makes from the page does. Export styling sets your font, with a bold face of its own, your logo, a first page with a background picture, a header and a footer each in its own colour, and your own CSS for the page body, for the whole site or per space where the site allows it. The Confluence page itself keeps Confluence's own design. - **How can I be sure which version of a Confluence page was approved?** Approve it by signing it with Oktul SignPlus for Confluence. The signing is tied to a SHA-256 hash of the space, the page and its version number, the signed document is attached to the page, and the byline says Page signed but modified if anyone edits it afterwards. The byline says that the page changed, not what changed; the page history shows that. - **How does SignPlus help Rovo and other AI agents?** It keeps official documents in Confluence, where Rovo reads them, instead of in a separate document system where copies go out of date. Each signature is tied to the page version, the signed document is attached to the page, and the page can stay read-only after signing. Webhooks tell another system when a signing completes or a signed page is edited, and the REST API starts a signing from one. SignPlus itself runs no AI model and sends nothing to one. - Privacy notice: https://oktul.com/docs/plugins/signplus/privacy/ - Sends data outside Atlassian, to: Dokobit; Zoho Corporation Pvt. Ltd (Oktul’s mailbox); Your own webhook addresses. What each receives and keeps is in the privacy notice. - CSA STAR Registry, Level 1: a completed CAIQ Lite v4.1.0 self-assessment, all 138 questions, published by the Cloud Security Alliance. A self-assessment rather than an audit, and not every answer is yes: https://cloudsecurityalliance.org/star/registry/oktul-ou/services/oktul-signplus-for-confluence - [Oktul Work Item Macro for Confluence](https://oktul.com/apps/work-item-macro/index.md): Show Jira work items on Confluence pages, any field as a column. Host: Confluence Cloud. - Documentation: https://oktul.com/docs/plugins/work-item-macro/ - Video: [Oktul Work Item Macro for Confluence](https://oktul.com/videos/work-item-macro/), 28 seconds, no sound - Marketplace listing: https://marketplace.atlassian.com/2371213272 - Price (Marketplace, 21.10.2026): USD 0.19 per user per month for 11–100 users, free up to 10 users. Costs less than STAGIL Tasks at every size up to 10,000 users. Costs less than Advanced Issue Macro at every size up to 10,000 users. It shows Assets objects in the table, renames columns and changes how a field is formatted, none of which Confluence's built-in Jira work items macro does. The Advanced edition is the Standard price plus 5%, and at least USD 0.01 more per user. - Questions it answers: - **Why does Confluence's Jira work items macro not show Assets objects?** Confluence Cloud's built-in Jira work items macro does not display Jira Service Management Assets fields. Atlassian tracks it as suggestion CONFCLOUD-80484, open since January 2025, and documents Assets on a page as a separate macro. Oktul Work Item Macro for Confluence lists the same work items with each Assets object in its column: the object type's icon, its label linked to the object, and its key or an attribute you choose. - **How do I show an Assets field in a table of Jira work items in Confluence?** Insert Oktul Work Item Macro on the page by typing /oktul, write the JQL query, and add the Assets field under Columns with Add column. Each object appears as a chip with its icon, label and key, read with the permissions of the person viewing the page. Jira Service Management with Assets has to be on the same Atlassian site. - **How is it different from Confluence's own Jira work items macro?** It shows Assets objects and draws Oktul Work Item Selector fields as work item cards. A page editor can rename every column heading and choose how each field is displayed. In the Advanced edition, you can edit text, dates, selects, people, estimates, status, Assets objects, rich text and Work Item Selector fields in the table. The built-in macro edits some standard fields inline and does none of the rest. - **How does Work Item Macro help Rovo and other AI agents?** It replaces the Jira table pasted into a Confluence page, which goes out of date and shows everyone what its author could see. The macro stores only the JQL query and reads Jira each time the page is opened, as the reader, with Assets objects and Oktul Work Item Selector fields. The page stays correct without an automation rule or a manual update. The app runs no AI model and sends nothing to one. - Privacy notice: https://oktul.com/docs/plugins/work-item-macro/privacy/ - Runs on Atlassian: granted by Atlassian, per application, to apps that store data only on Atlassian's infrastructure and declare no external hosts. Not a company-wide claim: https://developer.atlassian.com/platform/marketplace/runs-on-atlassian/ - CSA STAR Registry, Level 1: a completed CAIQ Lite v4.1.0 self-assessment, all 138 questions, published by the Cloud Security Alliance. A self-assessment rather than an audit, and not every answer is yes: https://cloudsecurityalliance.org/star/registry/oktul-ou/services/oktul-work-item-macro-for-confluence - [Oktul Regex Field for Jira](https://oktul.com/apps/regex-field/index.md): Jira fields that fill themselves in from the form, and only accept your format. Host: Jira Cloud. - Documentation: https://oktul.com/docs/plugins/regex-field/ - Video: [Oktul Regex Field for Jira](https://oktul.com/videos/regex-field/), 28 seconds, no sound - Status: submitted to Atlassian. The Marketplace listing awaits approval, so it cannot be installed yet. - Price (Marketplace, 21.10.2026): free, with no paid edition. Costs less than RegEx & Picker Fields at every size up to 10,000 users. Free, with every feature on every site: the rules, strict input, the paragraph field, JQL search and prefill. There is no paid edition. - Questions it answers: - **How do I dynamically fill Jira fields on the portal or the create screen?** With a field of the type Oktul Regex Field. In the field context's Prefill, write a template with smart values: {{user.displayName}}, {{user.email}}, {{user.accountId}}, {{today}}, {{today.iso}}, {{now}}, {{project.key}}, {{project.name}} and {{issueType.name}}. Any other field on the form works by its id or name, such as {{summary}}, {{customfield_10070}} or {{Cost centre}}, and so does a part of its value, such as {{Reporter.emailAddress}}. The field fills in on the create screen, the portal request form and transitions. It follows the fields it names until the person changes it, and stays empty when the value would break its rules. It fills its own field, not Jira's other fields. Assets fields cannot be used yet, because Jira passes none to an app's UI modification (FRGE-2079). - **How do I validate a Jira text field with a regular expression?** Jira Cloud's own text fields have no regex rule. Create a field of the type Oktul Regex Field (Single line), open its context settings, choose Advanced and enter the pattern. Jira then checks every value against it when it is saved, from any screen, the REST API, an import or Automation, and shows your message when a value does not match. - **Can a Jira field format a phone number or code as it is typed?** Yes, the single-line field can. Set a format such as 999-9999 and turn on strict input. Characters that do not fit are refused and the fixed ones are typed for you: 1234567 becomes 123-4567. Strict input works where Jira shows the app's editor. Jira Forms, the mobile apps and imports use a plain text box, and the rules still apply when the value is saved. - Privacy notice: https://oktul.com/docs/plugins/regex-field/privacy/ - CSA STAR Registry, Level 1: a completed CAIQ Lite v4.1.0 self-assessment, all 138 questions, published by the Cloud Security Alliance. A self-assessment rather than an audit, and not every answer is yes: https://cloudsecurityalliance.org/star/registry/oktul-ou/services/oktul-regex-field-for-jira ## Documentation ### Oktul Work Item Selector for Jira (Jira Cloud) - [Oktul Work Item Selector for Jira](https://oktul.com/docs/plugins/work-item-selector/index.md): A Jira Cloud custom field that offers only the work items a JQL query returns, single or multi select, with Automation, JQL functions and a workflow validator. - [Install the app](https://oktul.com/docs/plugins/work-item-selector/install/index.md): Installing Work Item Selector into Jira Cloud from the Atlassian Marketplace, confirming it worked, and what happens when the licence lapses. - [Create a Work Item Selector field](https://oktul.com/docs/plugins/work-item-selector/set-up-the-field/index.md): Creating an Oktul Work Item Selector field in Jira Cloud, choosing single or multi select, configuring its context and putting it on a screen. - [Moving from Issue Picker for Jira](https://oktul.com/docs/plugins/work-item-selector/moving-from-issue-picker/index.md): Moving from Issue Picker for Jira to Work Item Selector: add the new field beside the old one and copy the selections with one Automation rule. - [Limit the field with a JQL scope](https://oktul.com/docs/plugins/work-item-selector/jql-scope/index.md): The JQL query that decides which work items an Oktul Work Item Selector field offers in Jira, per field context, with placeholders for the work item and person. - [Permission mode](https://oktul.com/docs/plugins/work-item-selector/permission-mode/index.md): Whether an Oktul Work Item Selector field searches Jira with the viewer's permissions or the app's, and exactly what each mode exposes, the portal included. - [Automation and JQL](https://oktul.com/docs/plugins/work-item-selector/automation-and-jql/index.md): The Automation action that writes a Work Item Selector field, the four JQL functions, and the smart values and search aliases that read a selection back. - [Workflow validation](https://oktul.com/docs/plugins/work-item-selector/workflow-validation/index.md): Five dependency rules a transition can enforce on a Work Item Selector field, and what the cycle check does when the graph is too large. - [Compared with other work item pickers](https://oktul.com/docs/plugins/work-item-selector/compare/index.md): Work Item Selector beside other work item pickers for Jira Cloud, one capability per row, with what each row means and where it is documented. - [Privacy and data handling](https://oktul.com/docs/plugins/work-item-selector/privacy/index.md): What Work Item Selector stores, where it stores it, and what leaves your Atlassian ecosystem. Nothing does. - [Security assessment](https://oktul.com/docs/plugins/work-item-selector/caiq/index.md): Work Item Selector's completed CSA CAIQ Lite assessment, published in the Cloud Security Alliance STAR Registry. - [Release notes](https://oktul.com/docs/plugins/work-item-selector/release-notes/index.md): Every released version of Oktul Work Item Selector for Jira, newest first. ### Oktul SignPlus for Confluence (Confluence Cloud) - [Oktul SignPlus for Confluence](https://oktul.com/docs/plugins/signplus/index.md): Sign a Confluence page with a qualified electronic signature through Dokobit, and see later whether the page still matches what was signed. - [Install the app](https://oktul.com/docs/plugins/signplus/install/index.md): Installing SignPlus into Confluence Cloud, choosing the signing mode, connecting Jira if you want it, and what happens when the licence lapses. - [Configure SignPlus](https://oktul.com/docs/plugins/signplus/configure/index.md): Set up SignPlus for Confluence: the signing mode and Dokobit token, each site setting and its default, who may delete a signing, and what a space may change. - [Sign a page](https://oktul.com/docs/plugins/signplus/sign-a-page/index.md): How to sign a Confluence page with SignPlus and a qualified electronic signature, for named people or a whole group, and what each option does. - [What a signer sees](https://oktul.com/docs/plugins/signplus/for-signers/index.md): What a person asked to sign a Confluence page with SignPlus sees: the invitation, the Dokobit signing page, and how to check the signed file afterwards. - [After signing: check, download, cancel](https://oktul.com/docs/plugins/signplus/after-signing/index.md): What SignPlus shows on a signed Confluence page, how an edit after signing shows, where the signed file is, and who can cancel or delete a signing. - [Style the exported document](https://oktul.com/docs/plugins/signplus/export-styling/index.md): Give signed and exported Confluence documents your corporate visual identity: typeface, first page, header, footer, your own CSS, and what a space may restyle. - [What the document contains](https://oktul.com/docs/plugins/signplus/what-prints/index.md): How SignPlus turns a Confluence page into the document people sign, what it reproduces from the page, and where a PDF cannot follow Confluence. - [Automation and webhooks](https://oktul.com/docs/plugins/signplus/automation/index.md): Starting a SignPlus signing or exporting a PDF from an automation rule, and the two webhooks SignPlus sends when a signing completes or a page is edited. - [REST API](https://oktul.com/docs/plugins/signplus/rest-api/index.md): The SignPlus REST API: start and follow a signing, see who has not signed, export a PDF and fetch the signed document, from Code Studio, a Forge app or curl. - [Troubleshooting](https://oktul.com/docs/plugins/signplus/troubleshooting/index.md): What a SignPlus message means and what to do about it, for the people starting signings and for the administrators who configure it. - [Compared with other signing apps](https://oktul.com/docs/plugins/signplus/compare/index.md): SignPlus beside Digital Signature for Confluence and eSign Signatures for Confluence, one capability per row, with where each one is documented. - [Privacy and data handling](https://oktul.com/docs/plugins/signplus/privacy/index.md): What SignPlus stores, what leaves your Atlassian ecosystem, where it goes and why. The rendered document and each signer's name and email address go to Dokobit. - [Security assessment](https://oktul.com/docs/plugins/signplus/caiq/index.md): SignPlus's completed CSA CAIQ Lite assessment, published in the Cloud Security Alliance STAR Registry. - [Electronic signature terms](https://oktul.com/docs/plugins/signplus/signing-terms/index.md): What a signature made through SignPlus is, who provides it, what Oktul does and does not guarantee about it, and what the customer is responsible for. - [Release notes](https://oktul.com/docs/plugins/signplus/release-notes/index.md): Every version of Oktul SignPlus for Confluence, newest first, and what changed. ### Oktul Work Item Macro for Confluence (Confluence Cloud) - [Oktul Work Item Macro for Confluence](https://oktul.com/docs/plugins/work-item-macro/index.md): A Confluence macro that lists Jira work items for a JQL query, with the columns you choose, Assets objects as chips, and PDF and Word export. - [Install the app](https://oktul.com/docs/plugins/work-item-macro/install/index.md): Installing Oktul Work Item Macro for Confluence into Confluence and Jira on one site, and what happens when the licence lapses. - [Add the macro to a page](https://oktul.com/docs/plugins/work-item-macro/add-the-macro/index.md): Inserting the Work Item Macro on a Confluence page, writing its JQL query, choosing the columns, and what readers see. - [Columns and display options](https://oktul.com/docs/plugins/work-item-macro/columns/index.md): How each Jira field type is shown in the Work Item Macro, its default, and the display options its column offers. - [Assets and Work Item Selector fields](https://oktul.com/docs/plugins/work-item-macro/assets-and-work-item-selector/index.md): Show Jira Service Management Assets objects in a Confluence table of work items, which the built-in Jira macro cannot, and Work Item Selector fields as cards. - [Inline editing](https://oktul.com/docs/plugins/work-item-macro/inline-editing/index.md): Editing Jira fields in the Work Item Macro's table in the Advanced edition, as the reader and within their own Jira permissions. - [Export, page history and email](https://oktul.com/docs/plugins/work-item-macro/export/index.md): What the Work Item Macro puts in PDF and Word exports, page history and notification emails, and where it stops. - [Compared with the built-in Jira macro](https://oktul.com/docs/plugins/work-item-macro/compare/index.md): Oktul Work Item Macro beside Confluence's built-in Jira work items macro, which shows no Assets objects and cannot rename columns or change field formats. - [Privacy and data handling](https://oktul.com/docs/plugins/work-item-macro/privacy/index.md): What Oktul Work Item Macro for Confluence stores, where it stores it, and what leaves your Atlassian ecosystem. Nothing does. - [Security assessment](https://oktul.com/docs/plugins/work-item-macro/caiq/index.md): Work Item Macro's completed CSA CAIQ Lite assessment, published in the Cloud Security Alliance STAR Registry. - [Release notes](https://oktul.com/docs/plugins/work-item-macro/release-notes/index.md): Every version of Oktul Work Item Macro for Confluence, and what changed. ### Oktul Regex Field for Jira (Jira Cloud) - [Oktul Regex Field for Jira](https://oktul.com/docs/plugins/regex-field/index.md): Two Jira Cloud custom field types that only accept values matching a format, a length or a regular expression, enforced by Jira on every save. - [Install the app](https://oktul.com/docs/plugins/regex-field/install/index.md): Installing Oktul Regex Field for Jira into Jira Cloud, what it asks for, and how to check it worked. - [Configure the field's rules](https://oktul.com/docs/plugins/regex-field/configure/index.md): Setting the rules of an Oktul Regex Field for Jira field: simple rules, a regular expression, strict input, prefill and the error message. - [Fill fields dynamically](https://oktul.com/docs/plugins/regex-field/prefill/index.md): Oktul Regex Field for Jira fills a field on the create screen, the portal and transitions from the person, the date, the space and other fields on the form. - [Compared with other regex fields](https://oktul.com/docs/plugins/regex-field/compare/index.md): Oktul Regex Field beside RegEx & Picker Fields and Custom Fields Suite, one capability per row, with what each row means and where it is documented. - [Privacy and data handling](https://oktul.com/docs/plugins/regex-field/privacy/index.md): What Oktul Regex Field for Jira stores, where it stores it, and what leaves your Atlassian ecosystem. Nothing does. - [Security assessment](https://oktul.com/docs/plugins/regex-field/caiq/index.md): Regex Field's completed CSA CAIQ Lite assessment, published in the Cloud Security Alliance STAR Registry. - [Release notes](https://oktul.com/docs/plugins/regex-field/release-notes/index.md): Every released version of Oktul Regex Field for Jira, and what changed. ### Oktul Code Studio (Jira Cloud and Confluence Cloud) - [Oktul Code Studio](https://oktul.com/docs/plugins/code-studio/index.md): Write, store and run JavaScript and TypeScript scripts in Jira and Confluence Cloud on Atlassian Forge, with a sandbox that lists every change first. - [Install the app](https://oktul.com/docs/plugins/code-studio/install/index.md): Installing Oktul Code Studio for Jira or for Confluence, connecting the other product, the permissions it asks for, and what happens when the licence lapses. - [Administration](https://oktul.com/docs/plugins/code-studio/configure/index.md): Who may use Oktul Code Studio, the site settings, the console's administration sections, spaces, and exporting and importing the whole configuration. - [Moving from ScriptRunner for Jira Cloud](https://oktul.com/docs/plugins/code-studio/moving-from-scriptrunner/index.md): Moving from ScriptRunner for Jira Cloud to Oktul Code Studio: where each kind of script goes, how Groovy becomes TypeScript, and what has no equivalent. - [Script languages, publishing and Git](https://oktul.com/docs/plugins/code-studio/scripts/index.md): Writing Oktul Code Studio scripts in JavaScript, TypeScript and AssemblyScript: the script API, revisions, publishing and Git repositories. - [Writing scripts](https://oktul.com/docs/plugins/code-studio/writing-scripts/index.md): How to write an Oktul Code Studio script: what each trigger hands it, reading and writing Jira and Assets, the sandbox, long runs and results. - [Requests to other systems](https://oktul.com/docs/plugins/code-studio/requests-to-other-systems/index.md): How an Oktul Code Studio script calls other APIs with get, post, put, patch and delete, and reaches Atlassian endpoints the jira client cannot. - [Script API reference](https://oktul.com/docs/plugins/code-studio/script-api/index.md): Every global, type and value an Oktul Code Studio script uses, as the TypeScript declarations the console's editor reads. - [Script examples](https://oktul.com/docs/plugins/code-studio/script-examples/index.md): Complete Oktul Code Studio scripts to copy and adapt: a work item edit, an Assets migration, a register sync, scripted fields and a form rule. - [Snippets: starting points](https://oktul.com/docs/plugins/code-studio/snippets/starting-points/index.md): Oktul Code Studio script snippets for scripts started by a listener, an API trigger, a rule or a schedule, copied from the console and run by its tests. - [Snippets: scripted fields](https://oktul.com/docs/plugins/code-studio/snippets/scripted-fields/index.md): Oktul Code Studio script snippets for scripted fields: the value, the choices and the default, copied from the console and run by its tests. - [Snippets: dynamic forms](https://oktul.com/docs/plugins/code-studio/snippets/dynamic-forms/index.md): Oktul Code Studio script snippets for dynamic form rules: showing, requiring, limiting and filling fields, copied from the console and run by its tests. - [Snippets: work items](https://oktul.com/docs/plugins/code-studio/snippets/work-items/index.md): Oktul Code Studio script snippets for reading and changing work items, copied from the console and run by its tests. - [Snippets: search](https://oktul.com/docs/plugins/code-studio/snippets/search/index.md): Oktul Code Studio script snippets for searching work items with JQL, copied from the console and run by its tests. - [Snippets: Assets](https://oktul.com/docs/plugins/code-studio/snippets/assets/index.md): Oktul Code Studio script snippets for Assets objects and Assets fields, copied from the console and run by its tests. - [Snippets: Confluence](https://oktul.com/docs/plugins/code-studio/snippets/confluence/index.md): Oktul Code Studio script snippets for Confluence pages, copied from the console and run by its tests. - [Snippets: Service Management](https://oktul.com/docs/plugins/code-studio/snippets/service-management/index.md): Oktul Code Studio script snippets for Jira Service Management requests, copied from the console and run by its tests. - [Snippets: other systems](https://oktul.com/docs/plugins/code-studio/snippets/other-systems/index.md): Oktul Code Studio script snippets for requests to other systems through connections and approved hosts, copied from the console and run by its tests. - [Snippets: variables, storage and long runs](https://oktul.com/docs/plugins/code-studio/snippets/variables-storage-and-long-runs/index.md): Oktul Code Studio script snippets for script variables, stored values and runs that continue themselves, copied from the console and run by its tests. - [Snippets: AssemblyScript](https://oktul.com/docs/plugins/code-studio/snippets/assemblyscript/index.md): Oktul Code Studio snippets for AssemblyScript modules compiled to WebAssembly, as the console's Snippets dialog offers them. - [Sandbox and production](https://oktul.com/docs/plugins/code-studio/sandbox-and-production/index.md): How Oktul Code Studio's sandbox reads your site for real and lists every write instead of sending it, and what production runs and records. - [Triggers](https://oktul.com/docs/plugins/code-studio/triggers/index.md): Running an Oktul Code Studio script on a Jira or Confluence event, a schedule, a Jira automation rule or an HTTP request, and what each hands it. - [Fields and forms](https://oktul.com/docs/plugins/code-studio/fields-and-forms/index.md): Oktul Code Studio's scripted Jira fields, whose values a console script computes and stores, and dynamic forms, which run a script as a form changes. - [Connections and variables](https://oktul.com/docs/plugins/code-studio/connections-and-variables/index.md): How Oktul Code Studio scripts reach other systems: connections that hold the credential, script variables, and hosts an administrator approves. - [Rovo agents](https://oktul.com/docs/plugins/code-studio/rovo/index.md): The five Rovo agents in Oktul Code Studio, the translator, author, debugger, optimizer and editor, what each may do, and what they cost in Rovo credits. - [Teamwork Graph connector](https://oktul.com/docs/plugins/code-studio/teamwork-graph/index.md): What Oktul Code Studio sends to Atlassian's Teamwork Graph so Rovo finds your scripts, who can find each one, how it stays in step, and how to remove it. - [Groovy migration](https://oktul.com/docs/plugins/code-studio/groovy-migration/index.md): Moving ScriptRunner for Jira Cloud Groovy scripts to Oktul Code Studio: the Rovo translator converts each to TypeScript, and what it cannot convert. - [Limits](https://oktul.com/docs/plugins/code-studio/limits/index.md): Oktul Code Studio's limits on run time, requests, memory, events and storage, each with the Forge limit or the decision behind it. - [Compared with other scripting apps](https://oktul.com/docs/plugins/code-studio/compare/index.md): Oktul Code Studio beside ScriptRunner for Jira, Power Scripts and JMWE, one capability per row, with what each row means and where it is documented. - [Security](https://oktul.com/docs/plugins/code-studio/security/index.md): How Oktul Code Studio contains customer-written scripts, keeps credentials from scripts and browsers, and decides who may do what on the server. - [Privacy and data handling](https://oktul.com/docs/plugins/code-studio/privacy/index.md): What Oktul Code Studio stores, what leaves your Atlassian ecosystem, where it goes and why. Scripts reach only the hosts your administrator approves. - [Security assessment](https://oktul.com/docs/plugins/code-studio/caiq/index.md): Oktul Code Studio's completed CSA CAIQ Lite assessment, published in the Cloud Security Alliance STAR Registry. - [Release notes](https://oktul.com/docs/plugins/code-studio/release-notes/index.md): Every released version of Oktul Code Studio for Jira and for Confluence, and what changed. ## Support - [Help Center](https://oktul.atlassian.net/servicedesk/customer/portals): the support portal, public and without an account. It takes incidents, vulnerability reports, questions about the applications, demo requests, feature requests and requests for an application not yet built. A first response within 24 hours, Monday to Friday. Runs on Jira Service Management with EU data residency. - support@oktul.com: the same service desk by email, so a message here opens a request with a reference and the same response target. - legal@oktul.com: for a data protection request or a legal notice. No response target applies beyond the one-month period the GDPR sets for a data protection request. - hello@oktul.com: for anything that is not a support request or a legal matter. A person reads it, and no response target applies. ## Questions Oktul is asked - **Do Oktul applications send data outside the Atlassian ecosystem?** Only where a feature has to, such as signing a Confluence page, and then only what that feature needs. Everything else stays in your Atlassian ecosystem, because the applications run on Atlassian Forge, not on infrastructure we operate. The application’s documentation names every party that receives data and what it receives. - **How does Oktul test the security of its applications?** We test them ourselves. Before each release and on the 1st of every month, a workflow in our GitHub organisation scans the code of our applications and this website with Semgrep CE, npm audit, OSV-Scanner, gitleaks and zizmor, plus a type check that finds permission checks nobody awaits. Dependabot watches the dependencies of every repository. Code Studio and SignPlus have web triggers, the one kind of entry point Forge opens to anyone on the internet. We deploy them to a separate Forge environment on our test site and attack the triggers there with OWASP ZAP and our own probe. This website gets a passive ZAP scan. Each application also has a penetration test suite that lists the entry points in its code. We run it by hand before the application’s first release, then every six months and whenever an entry point is new or changed, and its automated checks run with every scan. Before each release we also review the application’s software bill of materials (SBOM): every package added, upgraded or removed since the last review, and every licence that needs reading. We give the SBOM to a customer who asks for it. - **Who at Oktul has access, and who can deploy a change?** We hold no account or credential on your site. Our own accounts are managed in one place, Zoho Directory, and every one uses multi-factor authentication. Each access is requested in Jira with a due date, reviewed before that date and removed unless it is extended. Only an application’s administrator, usually the owner of its code, runs forge deploy to put a version into production. We are introducing code owner review of every change. Our next security training is in February 2027. - **Do Oktul applications send data to an AI model?** No. None of our applications runs an AI model, and none sends your data to one outside Atlassian unless an administrator turns that on. Each application’s privacy notice lists every host it may contact. Work Item Selector, Work Item Macro and Regex Field declare none. SignPlus declares Dokobit, its signing provider. Code Studio declares the Git hosts it syncs with, Atlassian’s gateway, and each host a site administrator approves for a script. Code Studio’s five agents are Rovo agents, and Rovo is Atlassian’s AI: it reads your Jira and Confluence data under Atlassian’s terms, not ours. Code Studio’s tools also reach Claude or another MCP assistant, but only after an administrator turns them on, and what that assistant reads goes to its provider under your agreement with them. - **How do Oktul applications empower Rovo and other agentic teammates?** They keep the work in Jira and Confluence, where Atlassian’s Teamwork Graph and Rovo look for context. Work Item Selector writes each relationship to a work item property on both work items, which the Teamwork Graph reads. Work Item Macro reads Jira live, so a page never carries a stale copy. SignPlus attaches the signed document to the page it was signed from. Code Studio sends each script to the Teamwork Graph through a connector, with its own access rules, once an organisation admin connects the app. Rovo shows a script only to people who may open it in Code Studio. - **How did you check what Rovo and the Teamwork Graph do before building for them?** From Atlassian’s own Forge packages and developer documentation, read and dated, then held by tests in our code. Five findings decide what we build. A Forge app either publishes into the Teamwork Graph through a connector or queries it, never both. Atlassian accepts a connector only from an app installed into Jira. What a connector sends is visible to everyone on the site unless the app sends permissions of its own, so a connector we build restates the application’s own access and leaves out anything whose access it cannot state. A Rovo agent inside an app reads only through that app’s actions, as the person talking to it. An AI assistant outside Atlassian, such as Claude, reaches an app only through Atlassian’s MCP (Model Context Protocol) endpoint, after an administrator turns the app’s tools on. In the applications on this site, Work Item Selector writes each relationship to work item properties, which the Teamwork Graph reads. Work Item Macro reads Jira live, as the reader. SignPlus keeps signed documents on the page. Regex Field checks values in Jira. Code Studio’s Rovo agents read as the person talking to them and write drafts only, and its connector publishes scripts to the Teamwork Graph with Code Studio’s own permissions. None of them runs an AI model. - **Who maintains the applications, and what happens if they stop?** Solution architects named on the About us page, holding twenty-three Atlassian certifications and accreditations together. Oktul OÜ is registered in Estonia under registry code 17589681. The applications run exclusively in your Atlassian ecosystem. Atlassian runs the code on its own platform, and your configuration and data stay in your ecosystem whatever happens to us. - **How fast do you respond when something breaks?** An initial response within 24 hours, Monday to Friday, on a Help Center request. Raise one in the Help Center, or email support@oktul.com. It takes incidents, bugs, questions, demo and feature requests, and requests for an application we have not built yet. - **Why trust Oktul with a bank’s or a ministry’s Atlassian site?** Because we have spent years inside financial, public and private sector Atlassian ecosystems, and our applications solve the problems we met there. They run on Forge, so your ecosystem depends on no part of our infrastructure. - **Is Oktul an Atlassian partner?** Yes. Oktul is an Atlassian Marketplace Partner, with its own partner page on the Atlassian Marketplace. - **What does it cost to evaluate one?** Nothing. Every paid Oktul application has a 30-day free trial and is free for up to 10 users. Pricing and billing run through the official Atlassian Marketplace, so the charge lands on your existing Atlassian invoice and there is no new supplier to onboard. - **Who is Oktul?** Oktul OÜ is an Estonian company in Tallinn, registry code 17589681, and an Atlassian Marketplace Partner. Our architects have spent more than 14,000 hours implementing the Atlassian platform. - **Does our data leave Atlassian?** Only where a feature needs it. Work Item Selector, Work Item Macro and Regex Field send nothing outside Atlassian. SignPlus sends the page you sign to Dokobit, the signing service. Code Studio reaches the Git hosts it syncs with and any host an administrator approves for a script. - **Does Oktul hold security certifications?** Not yet. We are implementing an information security management system to ISO/IEC 27001 and expect to be certified by March 2027 at the latest. For the company and for Work Item Selector, SignPlus, Work Item Macro, Regex Field and Code Studio, we have completed the CAIQ Lite questionnaire and published it in the Cloud Security Alliance STAR Registry at Level 1. The [trust page](https://oktul.com/trust/) links the company entry, and each application's product page links its own. - **How fast does support answer?** We send the first reply to a [Help Center](https://oktul.atlassian.net/servicedesk/customer/portals) request within 24 hours, Monday to Friday. - **Do your apps use AI?** Only Code Studio. Its Rovo agents convert ScriptRunner Groovy scripts to TypeScript and find what is wrong with a script. They run on Rovo, Atlassian's AI. None of our apps runs an AI model of its own. ## Legal - [Privacy policy](https://oktul.com/legal/privacy/index.md): What Oktul does with the information you give us, and with the licence detail Atlassian passes on. - [Cookie notice](https://oktul.com/legal/cookies/index.md): One cookie is set without asking, and it holds your answer. Analytics and the support widget both wait for your permission. - [Website terms](https://oktul.com/legal/terms/index.md): The terms on which oktul.com is made available, and what you may do with what is on it. - [Application licence](https://oktul.com/legal/app-terms/index.md): The end user licence agreement (EULA) for Oktul applications installed from the Atlassian Marketplace. - [Data processing addendum](https://oktul.com/legal/dpa/index.md): The Article 28 processor terms for Oktul applications, published rather than sent on request. ## Languages - English: https://oktul.com/ - Estonian: https://oktul.com/et/ Documentation is English only. Every other page exists in English and Estonian as peers, and the Estonian pages are reviewed by a native speaker. ## Everything in one file - https://oktul.com/llms-full.txt