Description

When configuring Jira Automation rules (such as the "Edit issue" action), users rely on the field picker dropdown to select the appropriate fields to update.

Currently, the built-in field Due date is explicitly labeled as Due date (System) in the Automation field picker, making it easy to identify. However, the built-in Start date field is simply labeled as Start date without any indicator.

If an organization has created a custom field also named "Start date" (or similar), it becomes impossible to differentiate the native system field from the custom field within the Automation UI.

Suggested Solution

Update the Jira Automation field picker UI so that the native system field is explicitly labeled as Start date (System), standardizing it with the naming convention used for Due date (System).

Why this is important

• Reduces confusion: Helps administrators immediately identify the correct native field.

• Prevents errors: Minimizes misconfigured automation rules caused by accidentally selecting a duplicate custom field instead of the native roadmap/system field.

• UI Consistency: Ensures consistency across native field labeling within Jira Automation components.