Oktul home
  • English
  • Estonian

The documentation is in English only.

Contact us

Permission mode

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.

Permission mode decides whose permissions the picker searches with. Set it per field context in the Permissions section, beside the JQL scope.

Mode The picker searches as Effect
RESPECT_USER the person using it They see only work items they could already browse. The default, and the recommendation.
IGNORE_USER the application They can select work items they cannot normally browse.

A new context uses RESPECT_USER. IGNORE_USER is only ever an administrator’s explicit choice.

RESPECT_USER

The picker runs the scope as the viewer, so they see only what they could already browse.

A selected work item they cannot browse, or one that was deleted, shows as its key and Not available, with no link.

Use this mode unless you have a specific reason not to.

IGNORE_USER, and exactly what it exposes

This lets people select work items they cannot browse

The search runs as the app, so a person can select a work item they cannot open.

They see its key and the configured columns, nothing else. The key shows even without a Key column. No other field reaches their browser, and they cannot open the work item or read its comments.

Example: a support agent marks a request as blocked by engineering work in a space they cannot open. The alternative, browse access to the whole engineering space, exposes far more.

The JQL scope is the only limit here. Write it narrowly and choose columns with care.

Both modes apply on the portal

Portal customers get the configured mode, IGNORE_USER included.

  • Under RESPECT_USER a customer is offered their own requests within the scope: raised by them, shared with them or with their organisation. This uses the read:servicedesk-request scope. Until a site approves it, the picker says it cannot check, rather than guess.
  • Anonymous visitors always get RESPECT_USER, since they have no account.

Choosing

  • If a person selecting a work item they cannot open would be a problem, use RESPECT_USER.
  • If a person being unable to record a real dependency would be a problem, use IGNORE_USER, narrow the scope, and configure only the columns the decision needs.

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