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!

    105 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…)
    • 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…)
        9 comments  ·  GitLab CE  ·  Admin →
      • 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.

        24 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 →
        • 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

          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 →
          • Deploying to a PaaS

            To be able to deploy GitLab to a *PaaS*, i think GitLab should be more like a [Twelve-Factor App](http://12factor.net/config):

            * allow using environment variables for configuration (shouldn't be a problem to implement)
            * consider gitlab-shell as a backing service (e.g. make it possible to run on a different host)

            # Background

            I was trying to create a [Buildpack](http://devcenter.heroku.com/articles/buildpacks) for gitlab (see [amtrack/buildpack-gitlab](https://github.com/amtrack/buildpack-gitlab)) to be able to deploy GitLab to a *PaaS* like

            * [dokku](https://github.com/progrium/dokku)
            * [dokku-alt](https://github.com/dokku-alt/dokku-alt)
            * ~~heroku~~ (it has only an *ephemeral filesystem*)
            * and so on.

            But it…

            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…)
              3 comments  ·  GitLab CE  ·  Admin →
            • Remove issues and milestones

              Owner must have possibility to delete issues and milestones

              9 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 →
              • Don't guess rendered code block filetype and render with a single color

                Currently, the filetype of rendered code blocks is guessed if not explicitly given.

                There is of course no good heuristics for that, so we get ugly renderings like on the annexed screenshot.

                Viewing the page with the inspector shows that the guessed extension was.. vimscript!

                Let's disable that and render code blocks without explicit language with a single color.

                Live at: https://gitlab.com/gitlab-org/gitlab-development-kit/issues/15

                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…)
                • Trigger web hooks when using the respective web interface features

                  When defining web hooks for a specific action like tag push events, the web hook doesn't get triggered when creating a tag in the web interface.

                  This isn't exactly a "push", but does the same thing.
                  In my opinion, web interface actions matching the event(s) of a web hook should also trigger web hooks.

                  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…)
                    3 comments  ·  GitLab CE  ·  Admin →
                  • Extend Stats: Total Sum of Commits

                    Would be nice to extend the Stats for the Admin with "Total sum of commits".

                    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…)
                      4 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..

                      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…)

                        We’re accepting merge requests for this, please do so in the following steps in separate merge requests:

                        1. Add a filter for ‘authored by’ to issues and merge requests (so people can filter by this explicitly after we no longer show it in the list in step 2).
                        2. In the merge request list change ‘authored by’ => ‘assigned to’, if there is no assignee just show ‘Work In Progress’
                        3. Render ‘Work in Progress’ to the right of the Assignee dropdown on the merge request page show page
                        4. For bonus points: Change the button text on the merge request show page: ‘Accept Merge Request’ => ‘Assign to me and merge’

                      • Add View Pull Request buttons for Gmail

                        Add a subject-line link to view pull requests in Gmail. Github recently launched this feature and we would like to add it to the emails sent out by Gitlab.

                        https://github.com/blog/1891-view-issue-pull-request-buttons-for-gmail

                        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…)
                          2 comments  ·  GitLab CE  ·  Admin →
                        • Create merge result refs for merge requests

                          When a merge request is created, it has a ref. So it's possible to checkout, tests on them can be run in CI, etc.

                          However, it's possible that both the source and the target branches of a pull request compile and pass all tests, but the merge result doesn't. What is desired is ability to point the CI server _to the merge result_. I.e., an equivalent to Github's `refs/pull/<pull-request-id>/merge` ref.

                          See issue https://github.com/gitlabhq/gitlabhq/issues/7240 for previous discussion.

                          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…)
                            2 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…

                            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…)
                            • 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 →
                              • disallow merge of own merge requests/disable self-accept merge

                                Currently a developer can self-accept his merge request. It would be great to have an option to disable this on project level.

                                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…)
                                  2 comments  ·  GitLab CE  ·  Admin →
                                • Allow filtering on issue/merge request author/creator

                                  Who created the issue is a very important metric.

                                  GitLab allows only to filter by created by me, not by arbitrary users.

                                  Implement this for issues and merge requests.

                                  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…)
                                    3 comments  ·  GitLab CE  ·  Admin →
                                  • Red issue number in the tab

                                    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…)
                                      3 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…)
                                        2 comments  ·  GitLab CE  ·  Admin →
                                      • 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…)
                                        • Define IP address limit for deploy key, use system-wide-deploy-key

                                          use case is, when jenkins or another system, which need only read-only access to repository can't be (now) limiting by IP address. "Deploy" servers can be used by any developer and private key can be compromissed.

                                          Is possible add special system-deploy-key, which can add only administrator and can be used for any project?

                                          Is possible add param defined which IP address is allowed? (with use from="pattern-list" in authorization_keys file?)

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

                                          Feedback and Knowledge Base