Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
GitLab
GitLab
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 22,122
    • Issues 22,122
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 620
    • Merge Requests 620
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Packages
    • Packages
    • Container Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #8902

Project 'gitlab-org/gitlab-ee' was moved to 'gitlab-org/gitlab'. Please update any links and bookmarks that may still have the old path.
Closed
Open
Opened Dec 17, 2018 by Aric Buerer@abuerer
  • Report abuse
  • New issue
Report abuse New issue

As a GitLab instance admin, you can set up Jira development panel integration of all groups

Description

  • As a GitLab instance admin, you can set up Jira development panel integration of all groups, including the case if you are not a member of one of those groups.
  • That is, Jira development panel integration (in particular, able to see all GitLab repos via the dev panel in Jira) is possible for all these cases.

Original description

### Summary

When setting up the JIRA DVCS integration as the root user in GitLab, you are unable to access projects for a group that the root user is not a member of. The DVCS account is created in JIRA, but no projects will be added.

Steps to reproduce

  1. Create group that the root user is not a member of.
  2. Set up JIRA DVCS integration, authorizing as the root user in GitLab
  3. In JIRA, set up DVCS account for group that root is not a member of.

What is the current bug behavior?

Unable to access GitLab repositories in JIRA when root is not a member of the group.

What is the expected correct behavior?

All projects should be added in JIRA for a group the root user is not a member of.

Customer ticket: https://gitlab.zendesk.com/agent/tickets/110163 (internal use) I was able to reproduce this on my test instance. Once I added the root user to the group, I was able to update the DVCS account in JIRA and see the projects.

/cc @victorwu

Edited Dec 20, 2018 by Victor Wu

Related issues

  • Discussion
  • Designs
Assignee
Assign to
11.10
Milestone
11.10
Assign milestone
Time tracking
None
Due date
None
7
Labels
Enterprise Edition Jira Plan [DEPRECATED] backend customer devops::plan feature
Assign labels
  • View project labels
Reference: gitlab-org/gitlab#8902