Jira: Expose GitLab as virtual group to enable instance-level DVCS integration
Release notes
Jira Development panel is currently limited to GitLab namespaces and can't be connected to an entire GitLab instance.
GitLab account configuration for DVCS receives an additional field Instance name to expose to Jira, whose content will be provided to the Jira DVCS Connector as the Team or User Account.
Intended users
Customers who are relying heavily on Jira for planning, e.g.
- Cameron (Compliance Manager)
- Parker (Product Manager)
- Delaney (Development Team Lead)
- Rachel (Release Manager)
User experience goal
See Release notes above.
Proposal
See Release notes above.
Possible, the Project Alias feature is relevant here, although it is currently limited to SSH requests and a single project per alias.
Further details
In later iterations, some kind of N-to-M-mapping of GitLab projects and (sub)groups to different virtual namespaces might be an idea.
Permissions and Security
Documentation
See /docs/ links above.
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by Katrin Leinweber