Deprecated Feedback Forum

This is a deprecated feature request forum for GitLab CE/EE/CI features. As you can now vote on issues in GitLab, we’re moving the feature requests to the same project as we’re doing development in. This should make the step from request to development smaller and faster.

GitLab CE & CI feature requests

To submit a feature request for GitLab CE (including CI), please search and vote for or create an issue in the GitLab-CE project on GitLab.com: https://gitlab.com/gitlab-org/gitlab-ce/issues

GitLab EE feature requests

To submit a feature request for GitLab EE, please search and vote for or create an issue in the GitLab EE project on GitLab.com: https://gitlab.com/gitlab-org/gitlab-ee/issues

I don’t see my feature request on GitLab.com

If you don’t see your feature request on GitLab.com, feel free to create an issue on the issue tracker in the appropriate project and place a comment here to link it for everyone. Alternatively, most popular feature requests will have their issue linked from here in time.

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Allow custom mappings between LDAP and GitLab attributes

    When using LDAP authentication with GitLab, GitLab user attributes such as username, email and name are retrieved from the LDAP server by omniauth-ldap https://github.com/gitlabhq/omniauth-ldap/blob/master/lib/omniauth/strategies/ldap.rb . The mapping between GitLab attributes and LDAP attributes is currently fixed, except for the username (which is configured in gitlab.yml with ldap.uid).

    This feedback item proposes to allow mappings in gitlab.yml for 'name' and 'email' as well, e.g.

    name: 'cn'
    username: 'sAMAccountName
    email: '#{user.sAMAccountName}@example.com'

    28 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      2 comments  ·  GitLab EE  ·  Admin →
    • add protected branch option to "require merge request" regardless of permission level (ie: master)

      We like to give everyone full permissions, but want to prevent people from pushing to master without a merge request / code review (even masters)

      It would be nice to have an OPTION to require merge request

      26 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        2 comments  ·  GitLab EE  ·  Admin →
      • Extend support for JIRA issue tracker to set fix version

        When closing / resolving tickets via commit message it would be useful to be able to set a custom fix version as well (similar to the commands FishEye allows with https://confluence.atlassian.com/display/FISHEYE/Using+Smart+Commits).

        26 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          0 comments  ·  GitLab EE  ·  Admin →
        • Allow more control of permissions

          We need more granular permissions. Having the ability to define your own roles outside of the 'master, developer, reporter' defaults would provide a lot more control.

          For example, we would like developers to be able to create their own milestones but not push to protected branches.

          22 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            2 comments  ·  GitLab EE  ·  Admin →
          • Separate permissions for different tabs or views: "source code" view, "issue tracker" view, "wiki" view

            There should be an option for projects to expose its views ("source code", "wiki", "issue tracker", ...) with different permissions.

            There are already public, internal, and private access level for _entire_ project. This feature should allow hiding some parts of the project to project team only.

            One use case:
            Project team may want to make project (as title with description) and its "issue tracker" publicly discoverable while still keep source code private (only team members).

            One feature where separate permissions for views can be particularly useful is "releases" (especially for corporate world):
            http://feedback.gitlab.com/forums/176466-general/suggestions/4156755-releases-with-binary-files-like-on-github
            Without separate permissions for different views, "releases"…

            21 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              2 comments  ·  GitLab EE  ·  Admin →
            • Make all members of LDAP group GitLab admins

              In GitLab EE it would be nice if you could make everyone in a certain LDAP group GitLab administrators.

              For instance, you would have a LDAP group 'GitLab admins' and anyone added to that group would automatically become admin in GitLab.

              14 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                0 comments  ·  GitLab EE  ·  Admin →
              • Add statistics for Views/Pulls/Downloads

                I've had several users ask to be able to look at download statistics on their publicly available repositories so they are able to gauge popularity.

                14 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  1 comment  ·  GitLab EE  ·  Admin →
                • LDAP based user list

                  To see a user on various users lists, like when adding users to projects and giving them permissions, the user needs to be in local database. That requires a first login to GitLab by that user.

                  This is not practical and is not compatible with other software we use.

                  Someone already suggested LDAP only athentication (http://feedback.gitlab.com/forums/176466-general/suggestions/3788023-only-allow-login-via-ldap). Maybe combined with that an option to use LDAP as user database could be a doable solution?

                  Example of software supporting such options: JIRA, Confluence, OTRS, eGroupware...

                  This is of course an option for GitLab Enterprise Edition. I didn't see such category…

                  10 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    1 comment  ·  GitLab EE  ·  Admin →
                  • smaller fonts

                    It would be great to be able to make fonts smaller to make better use of screen real estate

                    7 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      0 comments  ·  GitLab EE  ·  Admin →
                    • send notifications on approvals

                      Notifications are sent on MR assignment and on merge but not on approval-requirement or approvals themselves, so developers need to reach out to individuals manually for approvals and poll their own MRs to determine when they're ready to merge.

                      An approval should be treated as an event with (1) notification to the approver(s) when they're required and (2) notification to the MR owner when approvals are granted.

                      7 votes
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        0 comments  ·  GitLab EE  ·  Admin →
                      • Any Cloud backup Software available?

                        When I mount a backup plan, I may choose to backup on a cloud device.I already use CloudBacko pro ,Google Drive and One Drive.
                        However, the only option I can select is CloudBacko pro.
                        Is there another cloud device on the market that would recognize?
                        Thanks.

                        6 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          0 comments  ·  GitLab EE  ·  Admin →
                        • Support signed pushes

                          See this SO for why signed pushes are needed: http://stackoverflow.com/questions/27299355/why-does-git-need-signed-pushes

                          Gitlab should enable support for signed pushes and also expose a UI for reviewing a project's push history (signed or not).

                          6 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            I agree to the terms of service
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                            0 comments  ·  GitLab EE  ·  Admin →
                          • Fix PivotalTracker integration

                            Currently, PivotalTracker tokens are added on a per-project basis. I'm guessing the thinking is that the owner of the PT project is also the owner of the GL project. Not necessarily the case at all.

                            If the GL project has multiple owners, everyone can see the PRIVATE PT token. This is a big security/privacy breach.

                            Any commits made which include the "[#<story id>]" tag then get added as activity originating from the token owner.

                            For example:

                            My Name
                            Commit by Teammate Name
                            https://gitlab.lab.somedomain.com/someteam/test/commit/8675309

                            Since everyone has one PT account, just have them input their token in their GL profile and…

                            6 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              I agree to the terms of service
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                              1 comment  ·  GitLab EE  ·  Admin →
                            • 6 votes
                              Vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                I agree to the terms of service
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                                6 comments  ·  GitLab EE  ·  Admin →
                              • Add a “start of week” option to milestone due date calendar

                                When adding/editing a project milestone, you are given the option of setting due date with a calendar interface.

                                Currently this calendar starts the week on Sunday. I’d like the option to customise this, as to me it makes more sense having Monday as the start of the week.

                                6 votes
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  I agree to the terms of service
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                  0 comments  ·  GitLab EE  ·  Admin →
                                • Can't how to vote merge requests

                                  There is no visible button to vote a merge request
                                  https://gitlab.com/noosfero/noosfero/merge_requests/45

                                  If only project members can vote than a notice should be displayed

                                  6 votes
                                  Vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    I agree to the terms of service
                                    Signed in as (Sign out)
                                    You have left! (?) (thinking…)
                                    3 comments  ·  GitLab EE  ·  Admin →
                                  • preserve image aspect ratio for group logos

                                    When uploading an image for a group logo, GitLab currently squashes it into a square, meaning it looks rubbish unless you happen to already have a square logo. It shouldn't be too difficult to preserve the image aspect ratio and just scale it accordingly...

                                    6 votes
                                    Vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      I agree to the terms of service
                                      Signed in as (Sign out)
                                      You have left! (?) (thinking…)
                                      0 comments  ·  GitLab EE  ·  Admin →
                                    • create a JIRA cross-referencing comment every time a JIRA issue is mentioned in GitLab

                                      GitLab EE already creates JIRA comments when closing JIRA issues. This could be extended to other mentions of JIRA issues. For example: I type 'See MYJIRA-123' in the description of a GitLab Merge Request, and in JIRA issue MYJIRA-123 a comment 'Referenced in Merge Request xxx' appears.

                                      5 votes
                                      Vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        I agree to the terms of service
                                        Signed in as (Sign out)
                                        You have left! (?) (thinking…)
                                        0 comments  ·  GitLab EE  ·  Admin →
                                      • Approval requests for individual files

                                        İt would be wonderful if we can define approval requests per file/directory basis.

                                        Usually some files are far more important than other files in most software systems. Simple bug on a report page does not affect the system much compared to a currency conversion bug on payment controller. If we can mark some packages/files/folders as approval required we can solve these problems.

                                        4 votes
                                        Vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          I agree to the terms of service
                                          Signed in as (Sign out)
                                          You have left! (?) (thinking…)
                                          0 comments  ·  GitLab EE  ·  Admin →
                                        • Add expand/collapse widgets on merge request "Changes" tab.

                                          Each Merge Request has a "Changes" tab. The content of that tab is a list of blocks, each of which consists of a file header & set of file changes. If there are numerous files, that layout has too much stuff in it. Can you add a widget in each file header to hide the changes for that file. Then I can quickly collapse the files I don't care about & focus on the ones I do.

                                          3 votes
                                          Vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            I agree to the terms of service
                                            Signed in as (Sign out)
                                            You have left! (?) (thinking…)
                                            0 comments  ·  GitLab EE  ·  Admin →
                                          ← Previous 1 3

                                          Deprecated Feedback Forum

                                          Feedback and Knowledge Base