Oktul home
  • English
  • Estonian

The documentation is in English only.

Contact us

Compared with other work item pickers

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.

Work Item Selector beside other Jira Cloud work item pickers. A tick means everything in the row’s definition; a partial cell names what is missing. Each app links to the Marketplace listing it was checked against.

CapabilityOktul Work Item Selector for Jira (opens in a new tab)OktulIssue Picker for Jira (opens in a new tab)codecentric AGWork Item Picker For Jira (opens in a new tab)FormineWork Item Picker - Custom Issue Picker Field for Jira (opens in a new tab)The Starware
Runs on AtlassianYesYesYesYes
Atlassian's native designYesNoYesNo
Permission modesYesYesNoNo
Choose the fields shownYesFixed set of fieldsYesFixed set of fields
Works on the create screenYesDoes not look nativeYesYes
Works on the customer portalYesDoes not look nativeYesYes
Its own Automation actionYesNoNoNo
Workflow validationYesNoNoNo
JQL functionsYesNoNoNo
Synced Jira linksYesDeleting a link keeps the selectionNoNo
Reverse lookupsYesNoNoNo

Checked on against each product's published documentation, its Marketplace listing where it has one, and testing. If a row no longer matches what an app does, write to hello@oktul.com (opens a new email) and we will check it again.

What each row means

Each definition links to the page that documents it.

Runs on Atlassian
A badge Atlassian grants on the Marketplace listing to every app that stores data only inside Atlassian and declares no external hosts. How Work Item Selector does it: Runs on Atlassian
Atlassian's native design
The picker, the selected work items and the configuration screens follow Atlassian's own visual design and user experience. End users cannot tell whether a part is Atlassian's or comes from the app. How Work Item Selector does it: Atlassian's native design
Permission modes
The administrator chooses whose permissions the search runs with. With the user's, people are offered only work items they can already open. With the app's, they can select work items their own permissions would hide. How Work Item Selector does it: Permission modes
Choose the fields shown
The administrator picks which fields each selected work item shows, from any field on the site rather than from a short list the app decides. How Work Item Selector does it: Choose the fields shown
Works on the create screen
The field can be filled in while the work item is being created, not only edited afterwards. How Work Item Selector does it: Works on the create screen
Works on the customer portal
Customers can fill in the field when they raise a request on a Jira Service Management portal. How Work Item Selector does it: Works on the customer portal
Its own Automation action
The app adds an Automation action, so an administrator sets the field by filling in a form rather than writing JSON into Jira's Edit work item action. How Work Item Selector does it: Its own Automation action
Workflow validation
A validator holds a transition until the selected work items meet conditions the administrator sets, such as their status or their project. How Work Item Selector does it: Workflow validation
JQL functions
The app adds JQL functions that find the work items a given work item selects, or the ones that select it, across every field or in one named field. How Work Item Selector does it: JQL functions
Synced Jira links
Each selection can be kept as a native Jira work item link, and removing either one removes the other. How Work Item Selector does it: Synced Jira links
Reverse lookups
Automation smart values and the REST API can read the dependencies in both directions: what a work item has selected and which work items have selected the current one. How Work Item Selector does it: Reverse lookups

A problem or a question? Write to support@oktul.com or open a request in the Help Center (opens in a new tab).