Jira Integration Form - Simplified UX

❌ Before

Jira

Connect to Jira for issue tracking

Jira URL

Email

API Token

Problems:

User must manually type Jira URL
User must manually type their email/username
3 empty fields to fill out
Generic placeholders, no helpful defaults

✅ After (Pre-populated)

Jira

Connect to Jira for issue tracking

Jira URL

Username

Your Jira login username (e.g., rh-dept-kerberos)

API Token

Create an API token at Jira Settings

Improvements:

✅ URL pre-filled with https://issues.redhat.com
✅ Username pre-filled with user's email
✅ Only API token needs to be entered
✅ All fields remain editable (not hardcoded)
✅ Better label: "Username" supports kerberos IDs

Key Changes

What's Better:

✅ Pre-population: Jira URL defaults to https://issues.redhat.com
✅ Smart defaults: Username pre-filled from user profile
✅ Still editable: All fields can be changed (not locked)
✅ Better labels: "Username" instead of "Email" (accepts kerberos)
✅ Faster setup: Only need to paste API token

Implementation Details:

• DEFAULT_JIRA_URL = 'https://issues.redhat.com'
• Pre-population happens via useEffect when form opens
• Username pulls from useCurrentUser() hook
• Fields remain fully editable for future multi-instance support

🔮 Future: Multiple Jira Instances

The current implementation keeps fields editable to support connecting to multiple Jira instances (up to 3):

Each instance will have its own name, URL, username, and credentials
Users can set a default instance for new sessions
New Session modal will include a "Jira Instance" selector
Pre-population will still work, but users can configure additional instances

See jira-multiple-instances-design.md for full design specification.