Per-Sentry-Project templates and default Jira project/fields for manual issue creation

Problem Statement

Currently, when creating a Jira issue manually from a Sentry issue ("Linked Issues" modal), the integration does not remember or allow configuration of per-project defaults:

• The Jira Project dropdown defaults to the first enumerated project rather than allowing each Sentry project to be linked to a preferred default Jira project.
• Selecting a Jira project prepopulates fields (like Priority) with fixed/unexpected defaults (e.g., High instead of Needs Triage), forcing developers to manually override values every time.
• In multi-team organizations, different teams have distinct Jira projects, workflows, and triage processes. Having a global integration configuration is insufficient for per-team workflows.

Solution Brainstorm

• Per-Project Default Jira Project: Allow each Sentry project settings page to configure a default linked Jira project so the modal automatically selects the right project.
• Per-Project Field Templates / Defaults: Allow teams to configure default values per Sentry project for manual issue creation (e.g., default Reporter, default Issue Type, default Priority mapping, and custom fields).
• One-Tap / Pre-Populated Creation: Ensure that clicking "Create Jira Issue" opens the form pre-filled with the team's predefined project defaults.

Product Area

Unknown

Start by tracing the Linked Issues modal and the Sentry project settings page, then determine where per-project Jira defaults would be configured and consumed. Done means manual Jira creation preselects the configured project and applies its field defaults for each Sentry project; the issue does not name files or tests to run.