Jira Integration Should Not Require Sharing Credentials per-project

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem to solve

The existing Jira integration requires that credentials for Jira be used by each project that wishes to integrate. (document: https://docs.gitlab.com/ee/user/project/integrations/jira.html) We are self-service on the Gitlab side, but not on the Jira side. If these credentials are JIRA-wide for all Jira Projects then very high level credentials would be required and shared with many individuals. If they are not, then a Jira user per-project needs to be setup - an administrative burden.

Further details

Proposal

Allow the credentials for jira to be stored safely and without exposing them. Then allow each project to simple add the user to their jira integration. This is how jenkins works with creds and similar to how Gitlab does site-wide deployment keys.

What does success look like, and how can we measure that?

Credentials are setup once on the Jira and Gitlab side by an administrator. All projects can interface with Jira by simply attaching credentials setup by the admin (that do not expose the credentials).

If necessary, allow multiple JIRA users creds to be setup in case the Jira side needs to setup a user per jira project to avoid cross-jira project access.

Links / references

Edited by 🤖 GitLab Bot 🤖