{
  "id": 16048964,
  "title": "How to set default field values in Jira Cloud (2026): every native workaround, compared",
  "url": "https://urgent.news/2026/10/22/how-to-set-default-field-values-in-jira-cloud-2026-every-native",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-22T13:36:24.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/loomwise/how-to-set-default-field-values-in-jira-cloud-2026-every-native-workaround-compared-26pg"
  },
  "original_language": "en",
  "account": "In Jira Cloud, setting default values for most system fields in company-managed projects remains a challenge. With over 2,800 votes on the request (JRACLOUD-4812) dating back to 2004, here are the current workarounds:\n\n1. Team-managed projects offer built-in default value functionality. In the project settings, navigate to Work types, select a type, click a field such as Description, Priority, or a custom field, and set the desired default. This can be done per work type.\n\n2. For the Priority field, utilize the Priority scheme in Jira Admin settings. Navigate to Work items and then Priority schemes. The default priority applies per project, not per work type.\n\n3. In company-managed projects with a Paragraph custom field, create a context default field and add it to the Create screen. Remove the system Description from the screen. Use a post-function or Automation to copy the field's value into Description upon creation. While functional, this approach requires a custom field, screen, screen scheme, and workflow edit for each variation.\n\n4. Automation is a viable option after creation. Set up a trigger that fires when a work item is created, followed by a condition based on the work type. Use an Edit work item action to apply the default values. This method is simple but has drawbacks, such as users not seeing the defaults during creation and the risk of overwriting user input, potentially exhausting automation run limits.\n\n5. Apps leveraging UI modifications APIs, such as Forge, can set field values directly in the Create dialog. This method ensures visibility while creating and remains per work type. However, the company-managed option incurs low setup costs, while the team-managed approach is more complex. Automation is a viable option, but apps are limited in number per project. A caveat is that issues created inline on boards and backlogs do not open the Create dialog, resulting in still-empty fields after creation. Loomwise, the company behind this report, developed a free app (https://loomwise.app/jira-default-values/) addressing these limitations.",
  "summary": "Jira Cloud still can't set a default value on most system fields in company-managed projects. The request (JRACLOUD-4812) has been open since 2004 and has about 2,800 votes. Here's what actually works today. 1. Team-managed projects: built in. Project settings → Work types → pick a type → click a field (Description, Priority, custom fields) → set the default. Per work type. Done. 2. Priority: the…",
  "key_points": [
    "Team-managed projects offer built-in default value functionality",
    "Priority field uses Priority scheme in Jira Admin settings",
    "Automation sets default values after creation with conditions"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}