What's the challenge?

When creating a merge/pull request from a Jira issue, the repository selector does

not retain the repository a user picked last time. Users who work across multiple

repositories in the same Jira project have to re-select the same repository on every

single create action, which is repetitive and error-prone. At our scale (500 users),

this adds up to significant repeated friction across teams.

We are aware of the existing "default repository per Jira project" setting in User

Settings. However, that requires each user to manually configure it in advance, and

it only allows one fixed default per project. It does not adapt to the repository a

user is actively working in.

How might we solve it?

When a user creates a merge/pull request and selects a repository, remember that

selection (per user, per Jira project) and pre-select it automatically in the

"Create merge/pull request" dialog the next time. In other words, treat the

last-used repository as an implicit, self-updating default — without requiring the

user to open User Settings and set it manually.

Ideally this would also apply to the "Create branch" dialog for consistency.

Environment: Jira Data Center 10.3.5, Git Integration for Jira 5.3.3, GitLab.

500-user license.