Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,767
    • Issues 44,767
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,330
    • Merge requests 1,330
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #233149
Closed
Open
Issue created Jul 31, 2020 by Patrick Deuley@deuley👽Contributor

Move GitLab for Jira app and DVCS Connector features to Core

What is the GitLab for Jira app?

GitLab for Jira is the Connect-based application that lives in the Atlassian marketplace.

What is the DVCS Connector?

The DVCS Connector is the Jira Software (self-hosted) equivalent of the Connect App feature. It allows developers similar functionality, but is more limited, and is only supported on self-hosted environments. Since Connect Applications are not available on self-hosted installations (at this time), this is currently the only option for these users.

Rationale

  1. Currently, we see an extremely low installation success rate for a variety of reasons, one of which is this pricing. It's a paid feature that isn't well-marketed by our application and this customer confusion leads to dissatisfaction.
  2. It's unlikely we'll expand the functionality dramatically. Today we simply push commit data over to their Connect API so that Jira is able to display detailed information about those commits from within the Jira API. We intend on expanding what data is sent, but won't be adding any other types of functionality.
  3. Providing more data to the Jira Connect API provides a significantly better experience for users that are integrating with Jira, and Atlassian is continuing to take that data and expand on the functionality available with it. This is a great win that requires little ongoing effort on GitLab's part.
Edited Aug 17, 2020 by Patrick Deuley
Assignee
Assign to
Time tracking