<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=342020) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal GitLab also shows a `Create new issue in Jira` button in the top right corner. The link behind this button is currently towards the generic "create new issue" page on Jira, basically the `CreateIssue!default.jspa` page on a Jira instance. Because just the generic page is used, Jira will prefill the `project` dropdown field with whatever Jira project you accessed last. This `project` dropdown field is not prefilled with the Jira project that has been associated with the GitLab repository. This creates some confusion: suppose a user might have been checking Jira issues within Jira of Jira project A. Then the user accesses the GitLab repository of project B and clicks on the `Create new issue in Jira` button => Jira will open the `create new issue` screen with Jira project A prefilled instead of project B. Customer may have hundreds of GitLab repositories and hundreds of Jira projects, so some prefilling with the correct Jira project would be handy. The way to have a link that immediately prefills the correct Jira project is by specifying the correct PID value of the Jira project as a get variable in the link. For example: `https://our-jira-server-here/issues/secure/CreateIssue!default.jspa?pid=10001` You can get Jira project id using this link https://confluence.atlassian.com/jirakb/how-to-get-project-id-from-the-jira-user-interface-827341414.html <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. -->