General

This feature request forum allows you to submit, comment on and vote for GitLab CE/EE/CI features.

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 vote and comment on it.

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

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

  • Hot ideas
  • Top ideas
  • New ideas
  1. Set due dates for individual issues

    Sometimes we add issues that are independent of a milestone. An example of this type of issue would be a bug or a question. I'd like to be able to set a due date for these individual issues without having to add them to a milestone. Thanks!

    80 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…)
    • Have a responsive design that scales to the full width

      I have a large and wide monitor, but some of the screens on GitLab don't expand to make use of available horizontal space. (The contents are in a fixed width block; the margins expand).

      Screens such as the milestone view and side-by-side diff view could immensely benefit from the extra space.

      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…)
        3 comments  ·  GitLab CE  ·  Admin →
      • Branded Login Page for CE

        Could you please add logo/branding to CE? What's the incentive behind restricting this to EE only?

        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…)
          4 comments  ·  GitLab CE  ·  Admin →
        • Request access procedure

          Normally the procedure for getting access to a repo. involves mailing the Owner(s) or creating a Ticket.

          We have found this to be slow and sometime people are not accessible, also it doesn't provide a good Audit trail.

          It would be preferable to have a workflow where you inside the tool can request access, like:

          $ ssh git@gitlab request <repo> <role>

          This then notifies the Owner(s) that can Grant this request.

          $ ssh git@gitlab [grant|reject] <request id>

          The advantage of this approach is that it better model's how permission's get assigned and it provides an Audit trail inside the tool.

          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…)
            7 comments  ·  GitLab CE  ·  Admin →
          • Create Merge Request flow - default to master unhelpful

            Upon pushing new commits, the Dashboard displays a helpful "Create Merge Request" button. In previous versions, this would take the user to a new page with the update branch pre-loaded as the Source Branch. The Target Branch would not yet be loaded, since this updated branch could be a feature branch or a hotfix branch not going straight into master. This was extremely helpful and the flow made a lot of sense.

            Now, in Gitlab 7.2.1, the flow has become cumbersome and unhelpful. The button takes the user to a page with the update branch preloaded in Source Branch and…

            8 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…)
            • Add Access-Control-Allow-Origin header to HTTPS pack-protocol responses

              I would love to be able to clone a repository from my web-based environment. I've gone through the trouble to implement the git database and network protocols in pure js so I have git in the browser, but I can't actually talk to your server because you haven't enabled CORS.

              I see your server is being proxied through nginx. This makes is trivial to enable this feature.

              https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS

              http://enable-cors.org/server_nginx.html

              I need to be able to request urls like https://gitlab.com/creationix/creationix.git/info/refs?service=git-upload-pack over XHR. The pack protocol involved GET and POST requests to this domain from another domain (where my app is hosted).

              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…)
              • Bubble description of a project while hovering on the "personal projects" columns

                UI Feature request to have a bubble offering the overview of each project listed in the "personal projects column" of the user front page, avoiding to have to click on the project to know what its description is.

                Move your mouse above the name of a project listed in the "personal projects" column of the user front page. Currently the color just turns blue, which is nice but does not offer added value for the user.

                Moving above the name of a project, a bubble could offer the description of the project, avoiding to have to click on the project…

                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…)
                • two-factor authentication with Yubikey

                  Implement a two-factor authentication mechanism with Yubikey to create secure Gitlab instances.

                  http://www.yubico.com/

                  The linux kernel source code is also protected by a Yubikey by the way:
                  http://www.zdnet.com/linux-kernel-source-code-repositories-get-better-security-7000032713/

                  16 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 CE  ·  Admin →
                  • Allow deletion of "mentioned in commit" messages which no longer exist

                    Gitlab 7.3 changed the old behavior where any message can be deleted, including commit references. I think this is a good thing.

                    But when a commit is force pushed an old commit can disappear, and is no longer useful to be referenced in the issue page. A delete button can be useful for these sorts of messages.

                    1 vote
                    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 CE  ·  Admin →
                    • Option to have Work In Progress filter for Issues

                      I want additional status for issues in git lab. For example, "work in progress".. It will be useful to track what are the issues currently in working phase. Also i want an option to revert back the status from work in progress to open..

                      1 vote
                      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…)
                      • provide composer package repository support

                        GitLab HQ should be more readily usable as a Composer package repository solution. By building this as a project service (akin to Hipchat or CI integration), projects can "opt-in" to be included in a generated packages.json manifest file.

                        I have successfully built the core of this functionality into our install of GitLab HQ CE 6.7.5 and would like to make it available to the GitLab community.

                        71 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…)
                          14 comments  ·  GitLab CE  ·  Admin →
                        • Show on index view merge requests can be automatically merged

                          Could be done with a small icon that represents the merge and that can have different colors:

                          - green: yes
                          - red: no

                          The first icon that comes to mind is GitHub's pull request icon: https://www.iconfinder.com/icons/298789/git_pull_request_icon#size=128 but I'm not sure if we can use that or not.

                          1 vote
                          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…)
                          • Allow Web Hooks to post back logs data that will be shown under a project "Log" section

                            Let's say you have defined a "Push events web hook" for one of your project on gitlab.

                            When Gitlab triggers the hook, this one may generates logs useful to the developer. Showing those logs under a project "Log" section would be nice (instead in an external other tool)

                            Implementation example (the basic one):

                            - Don't make Gitlab ignore the content returned by the hook when the HTTP call is executed (or let the hook post back data later to gitlab thanks to a secret "token" passed to it).

                            - Expect hooks to return JSON-formatted list of logs formatted as follow:

                            12 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 CE  ·  Admin →
                            • Support running gitlab in a subdirectory with omnibus

                              It would be nice if `external_url` would allow a path specification, because then you could install gitlab omnibus along other applications on the same server without using multiple subdomains.

                              38 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…)
                              • Send X-Github-Event on Push Web hook

                                Gitlab's web hooks for push events (https://github.com/gitlabhq/gitlabhq/blob/master/doc/web_hooks/web_hooks.md#push-events) are very similar to the ones created by Github (https://developer.github.com/v3/activity/events/types/#pushevent). By sending the `X-Github-Event: Push` like Github does (https://developer.github.com/v3/repos/hooks/) one could use existing implementations for Gitlab too. For example node-github-hook (https://github.com/nlf/node-github-hook/issues/15#issuecomment-55960389).
                                Similar: http://feedback.gitlab.com/forums/176466-general/suggestions/3787958-web-hooks-data-posts-should-be-github-compatible But I only want the X-Github-Event header field added :)

                                0 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 CE  ·  Admin →
                                • Native Debian (deb) and Fedora (rpm) packages

                                  There is an ongoing effort to make Fedora packages that is detailed on: https://fedoraproject.org/wiki/User:Axilleas/GitLab#GitLab_for_Fedora Please offer to help with the native packaging effort there.

                                  There also is an ongoing effort to make Debian packages on the Debian Ruby Mailing list: https://lists.debian.org/debian-ruby/ Please offer to help with the native packaging effort there.

                                  Some older Debian Ruby emails for reference:
                                  Status https://lists.debian.org/debian-ruby/2014/03/msg00027.html Cédric Boutillier <boutil@debian.org>
                                  Emoji https://lists.debian.org/debian-ruby/2014/03/msg00053.html Jonas Genannt <jonas.genannt@capi2name.de>
                                  Sytse offerting help https://lists.debian.org/debian-ruby/2014/03/msg00070.html

                                  20 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 CE  ·  Admin →
                                  • red issues

                                    The little circle with the number of issues in the "Issues" tab is the same colour as a background. It would be really useful if it can be made red(?) or maybe set a custom colour from a config somewhere. This would make issues pop-out and stand out on the page, otherwise they sort of blend into the background.

                                    Alex

                                    2 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 CE  ·  Admin →
                                    • Allow upload any filetype to the wiki

                                      Actually, you just can upload images to the wiki. It could work with other filetypes too in order to add docs in PDF or design files to the project wiki.

                                      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 CE  ·  Admin →
                                      • 1 vote
                                        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…)
                                        • rules for branch protection

                                          I miss a feature to have better protection on branches.
                                          More precise level of branch protection. So only specific users can push to specific branches.

                                          We have release branches, testing branches and production branches. I would like to have something to allow user group A to accept merge requests for release branches, user group B only to accept merge requests on testing branches and user group C only to accept merge requests on production branches.

                                          The branches could be recognized by simple rules: Release branches start with /release Testing branches end with _T Production branches end with _P

                                          2 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 CE  ·  Admin →
                                          ← Previous 1 3 4 5 37 38
                                          • Don't see your idea?

                                          Feedback and Knowledge Base