FAQ

Data and security

Where are the field values stored?

In Jira, as ordinary custom field values on the issue. The app stores only its configuration.

Does anything leave Atlassian?

No. This app declares no external network access at all.

Does it use AI?

No.

Does the app store any personal data?

No. It holds no Atlassian account ID, no name, no email address and no issue content. Its entire storage is one record listing which field contexts are delegated to project administrators — which is why it requests no personal-data reporting scope and has nothing to erase when an account is closed.

Is the Masked Input field encrypted?

No. It formats and validates input. The value is a normal Jira field value, visible to anyone who can see the issue. Do not store secrets in it.

What happens to my data if I uninstall?

Field values stay in Jira, because Jira owns them, and so does every field's configuration. The app runs an uninstall handler that empties its own storage — the one delegation record — before Atlassian detaches the installation's data and destroys it under its own retention policy. The field types stop rendering, so export anything you need to keep readable first. See Where your data goes.

What stops working if our licence lapses?

Four things, all of them administrative: adding, editing, reordering and deleting select list options. Plus two background jobs — issue links for a picker value set on the create screen, and the refresh of the Checklist-* values JQL searches. The fields themselves keep rendering and saving everywhere, and nothing already on an issue is touched.

How the fields behave

Can I search these fields in JQL?

Checklist progress, yes, through the Checklist-* values described on the Checklist page. Issue Picker and Masked Input behave like the Jira field types they are built on.

Do the fields work on the create screen?

Yes, if you add them to the create screen — and on transition screens, and in the Jira Service Management customer portal, both for filling a request in and for reading it back. The Issue Picker even creates its issue links for values set at creation time, a moment after the issue exists.

Do they appear in exports and reports?

They are Jira field values, so they appear where Jira field values appear. Complex values such as checklists export as their stored text, not as a formatted list.

Can several checklists live on one issue?

Yes. One Checklist field can hold several named checklists, and you can also create more than one Checklist field.

Does it work with team-managed projects?

The field types are created and configured centrally, through field contexts, which is a company-managed concept — so use company-managed projects for the full feature set. The Checklist Completion Validator is the exception: it is declared for team-managed projects as well as company-managed ones.

Delegating select list options

Can a project admin break another project's field?

No. Delegation is only offered for contexts limited to a single project, so the options they edit apply to their project only.

Why is my select field not in the list?

Most likely it has no project-scoped context — create one and it appears. Two other possibilities: the site has more custom fields than could be read in one request, in which case the screen says so and the search box will find it; or the field is not one of the four supported types (Select List single or multiple, Checkboxes, Radio Buttons).

Can I see who changed an option?

Option changes are configuration changes made through Jira, so they follow Jira's own audit log rather than an app-specific log.