Default field values in the Jira Cloud Create dialog — user guide, privacy policy and support.
App: Smart Defaults for Jira Cloud
Last updated: 15 October 2026
Smart Defaults is an Atlassian Forge app. It runs on Atlassian’s infrastructure. It has no servers of its own, makes no requests to other hosts, and sends no data to any third party. What the app stores stays inside the Forge platform and your Jira site.
The app declares no external permissions in its manifest (no egress), which makes this verifiable rather than a promise.
When an administrator saves a rule, the app stores it in Forge storage:
| Data | Why |
|---|---|
| Project ID and name, issue type ID and name | To show which rule belongs where |
| For each field in the rule: field ID, field name, type, the default value, and the “replace a value that is already filled” setting | To fill the Create dialog |
| For people fields: the Atlassian account ID (names are looked up in Jira when the editor shows them, not stored) | To fill Assignee, Reporter and user pickers |
| The ID of the Jira UI modification that carries the rule | To update or delete it |
| The time of the last change and the account ID of the person who made it | To show when the rule was updated and to keep a record of who changed it |
Default values are whatever the administrator typed, so they may contain any text the administrator chose to enter.
The same values are also stored in your Jira site as a UI modification
created by the app (its name is smart-defaults; it carries the field values and
the project and issue type it applies to). Jira stores it as part of your site.
The app does not store passwords, email addresses, payment details, or the contents of issues.
Using the permissions of the person who is using the app:
As the app itself, it reads the list of UI modifications that the app has created (Jira returns only those).
In the Create dialog the app also reads the create screen’s allowed values (options, components, versions), so that it never inserts a value that has been deleted.
The app does not create or change issues.
The app contains no analytics, no tracking pixels, no advertising and no third-party scripts. It does not profile users and makes no automated decisions about them.
In Forge’s storage, operated by Atlassian, and in your Jira site. Hosting location and residency follow the Atlassian Cloud infrastructure your site runs on. See the Atlassian Trust Center for details.
Since the app processes data on behalf of your organisation, requests for access, correction or deletion of personal data are best raised with your own Jira administrator, who controls the site. We will assist administrators with any such request — contact info@vudia.site.
Material changes will be published on this page with an updated date above.
Vudia — info@vudia.site