# Install the app

Work Item Selector is an Atlassian Forge application. Installing it adds two custom
field types to your Jira Cloud site. Nothing is deployed to your own infrastructure,
and nothing runs outside Atlassian.

**Jira Cloud only.** There is no Data Center or Server version, and none is planned.

## Requirements

- Any Jira Cloud application (including collections and standalone products)
- Organisation administrator permission

## Install it

<Steps
  items={[
    {
      title: 'Open the Marketplace listing',
      body: 'Two field types ship together in the one application, Single Select and Multi Select.',
    },
    {
      title: 'Select Try it free, at the top right',
      body: 'Evaluation runs through Atlassian rather than through Oktul.',
    },
    {
      title: 'Choose your site in the dialog, then Install',
      body: 'Forge applications take up to a minute to become available. Installing also backfills the relationship index for work items that already hold values, so the graph is not empty for anything predating the install.',
    },
    {
      title: 'Use the field',
      body: 'Create it, scope it, and put it on a screen. See set up the field.',
    },
  ]}
/>

## Confirm it worked

Go to **Settings**, the gear icon at the top right, then **Work items**. Open
**Fields** in the left menu and select **Create new field** at the top right. Both
field types should be listed:

| Field type | Holds |
|---|---|
| **Work Item Selector (Single Select)** | exactly one work item |
| **Work Item Selector (Multi Select)** | up to 100 work items |

Creating a field is the next step, and it needs a JQL scope before it offers anything.
See [set up the field](../set-up-the-field/).

## Licensing, and what happens when it lapses

Paid through Atlassian, licensed per installation via the Marketplace. Evaluation runs
through Atlassian, not through Oktul.

With no active subscription, every user-facing surface is blocked and says where to fix
it: the picker, the issue view, the configuration screen, the Automation action, search
suggestions and the JQL functions.

<Aside type="note" title="Two things deliberately keep working">
**Workflow transitions still succeed.** Blocking them would turn a billing lapse into a
site outage that the person hitting it cannot fix.

**Background indexing keeps running**, so the relationship graph is still correct when
the licence returns.

**No field value is ever written or cleared on the unlicensed path.** Selections stay
intact and reappear the moment the subscription is active again.
</Aside>

## Removing the app

<Aside type="caution" title="Field values go with the field type">
Uninstalling removes both custom field types, and Jira removes the stored values with
them, as it does for any custom field. **Export anything you need first.**

Forge storage, which holds each field context's configuration, goes with the
application. Nothing is retained outside your instance, because nothing was ever stored
outside it. See [privacy and data handling](../privacy/).
</Aside>

## Related

- [Set up the field](../set-up-the-field/)
- [JQL scope](../jql-scope/)
- [Permission mode](../permission-mode/)
- [Automation and JQL](../automation-and-jql/)
- [Workflow validation](../workflow-validation/)
- [Privacy and data handling](../privacy/)

---

A problem or a question? Write to [support@oktul.com](mailto:support@oktul.com) or open a request in the [Help Center](https://oktul.atlassian.net/servicedesk/customer/portals). Both reach the same service desk, so either way the request gets a reference and an SLA measuring the response.