GitLab issueshttps://gitlab.com/gitlab-org/gitlab/-/issues2023-09-21T12:52:13Zhttps://gitlab.com/gitlab-org/gitlab/-/issues/191Vacation API2023-09-21T12:52:13ZValery SizovVacation APII think it would be cool to have an alert when you mention some user which is on vacation or have day off. It would be really useful for big company including us :)
Also this feature can be integrated with calendars.
@dzaporozhets @dbl...I think it would be cool to have an alert when you mention some user which is on vacation or have day off. It would be really useful for big company including us :)
Also this feature can be integrated with calendars.
@dzaporozhets @dblessing @sytseshttps://gitlab.com/gitlab-org/gitlab/-/issues/14194Slack channel should show helpful text when linking to private repos2024-01-15T09:35:28ZArno FlemingSlack channel should show helpful text when linking to private repos## Description
In order to not get distracted, as a receiver of a link, I don't see a sign in text when my colleague shares a private repo.
```cucumber
Given I have a private repo
When I share a link to that repo (on slack in this inst...## Description
In order to not get distracted, as a receiver of a link, I don't see a sign in text when my colleague shares a private repo.
```cucumber
Given I have a private repo
When I share a link to that repo (on slack in this instance)
Then I do not see
'GitLab
Sign in
GitLab.com'
But I see some nice words from gitlab about this repo being private
```
## Example
Current situation is like this:
![Screenshot_from_2016-01-14_11-21-05](/uploads/0e0ca1745712d8e45e88daa53717ee68/Screenshot_from_2016-01-14_11-21-05.png)
## Proposal
## Links and reference
- https://gitlab.my.salesforce.com/0016100000KvahJ
- https://gitlab.my.salesforce.com/00161000004zoBW
## Note
This issue will be ~"solved by another issue" / addressed by https://gitlab.com/gitlab-org/gitlab/-/issues/339906Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/14885Sign-in with google_oauth2 auth failed2023-10-16T21:04:04ZJW BellSign-in with google_oauth2 auth failedI created an account on gitlab.com via my github.com auth credentials.
When trying to sign-in using my google.com credentials the error page says:
"Try logging in using your email/username, try recovering password. If neither works try...I created an account on gitlab.com via my github.com auth credentials.
When trying to sign-in using my google.com credentials the error page says:
"Try logging in using your email/username, try recovering password. If neither works try contacting the GitLab administror." (to paraphrase)
The error page should mention the account might have been created using github.com, bitbucket.org, etc, auth credentials.
![gitlab-signin-failed](/uploads/1fc4e807367e04afe39b1110afff6568/gitlab-signin-failed.png)https://gitlab.com/gitlab-org/gitlab/-/issues/14888Webhook: add uuid header to differenciate requests2023-12-07T20:57:50ZSebastien MALOTWebhook: add uuid header to differenciate requestsHi,
I don't know if webhooks are stored into postgresql database, but it should be interesting to add a uuid token for each of them to differenciate and send it with request.
Like that, if a request is resent, we will be able to detect...Hi,
I don't know if webhooks are stored into postgresql database, but it should be interesting to add a uuid token for each of them to differenciate and send it with request.
Like that, if a request is resent, we will be able to detect it.
On Bitbucket platform, another header is added which display the count of send.
First sent :
````
X-Hook-Uuid: 908a6d9e-45fd-46c8-97e6-c4f350f219dd
X-Attempt-Number: 1
````
Second sent :
````
X-Hook-Uuid: 908a6d9e-45fd-46c8-97e6-c4f350f219dd
X-Attempt-Number: 2
````
In the future, it should be too valuable to expose new webservices in the API to list all recent requests or the retrieve an old payload using uuid token.
Can you generate both additionnal headers ?
Many thanksBackloghttps://gitlab.com/gitlab-org/gitlab/-/issues/14889Notification center2024-01-11T09:28:59ZSid SijbrandijNotification centerI'm writing this under verbal pressure from Job.
This is separate from the action center. And Dmitriy is opposed to it.
The notification center will show the same notifications as email. You can disable emails or use both emails and th...I'm writing this under verbal pressure from Job.
This is separate from the action center. And Dmitriy is opposed to it.
The notification center will show the same notifications as email. You can disable emails or use both emails and the notification center. Issues and merge requests you viewed will be marked as read, even if you arrived at them via another channel. This will probably mean an extra database call for every issue/MR/commit/etc. load.https://gitlab.com/gitlab-org/gitlab/-/issues/14892Support AsciiDoc for issue, merge request, epci descriptions and comment2023-01-18T08:31:54ZFlorian WilhelmSupport AsciiDoc for issue, merge request, epci descriptions and commentI would like to be able to use AsciiDoc as markup-language in the whole application, including issues and MRs.
A global switch for the default setting (Markdown or AsciiDoc) would be great. For every multi-line text input, there should ...I would like to be able to use AsciiDoc as markup-language in the whole application, including issues and MRs.
A global switch for the default setting (Markdown or AsciiDoc) would be great. For every multi-line text input, there should be an option to chose the alternative (as in not-default) markup language.
## related
- [better asciidoc rendering](https://gitlab.com/gitlab-org/gitlab-ce/issues/14209)
[Cf](https://twitter.com/gitlab/status/689147078203846656)https://gitlab.com/gitlab-org/gitlab/-/issues/14896Add tips for wrangling Rails 'remote IP' detection2023-08-01T16:18:46ZKelvin MutumaAdd tips for wrangling Rails 'remote IP' detectionDev: https://dev.gitlab.org/gitlab/gitlabhq/issues/1838
Once every while a user has a network setup where Rails (or rather Rack) incorrectly detects the remote IP of requests. This can have several unwanted consequences:
- a default re...Dev: https://dev.gitlab.org/gitlab/gitlabhq/issues/1838
Once every while a user has a network setup where Rails (or rather Rack) incorrectly detects the remote IP of requests. This can have several unwanted consequences:
- a default remote IP of 127.0.0.1, increasing the risk of inadvertent throttling / banning of IP's by Rack::Attack
- `ActionDispatch::RemoteIp::IpSpoofAttackError`
I think we can advise people to do the following:
1) Make sure your proxy (proxies) sets `X-Forwarded-For` (the default NGINX config for GitLab does this correctly nowadays)
Example:
```
location @gitlab {
# snip
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
```
2) If you will be accessing your GitLab server from a private network (e.g. your client is 192.168.x.y) then let your proxy set `Client-IP` in addition to `X-Forwarded-For`.
Example:
```
location @gitlab {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Client-IP $remote_addr;
}
```
Related MR: https://dev.gitlab.org/gitlab/gitlabhq/merge_requests/1328
### Extra Step
Document 127.0.0.1 whitelist
cc/ @jacobvosmaer @sytses @axilBackloghttps://gitlab.com/gitlab-org/gitlab/-/issues/14866Project#default_branch is rather slow in certain cases2019-11-06T04:21:21ZYorick PeterseProject#default_branch is rather slow in certain casesThis particular method appears to take up quite some time as per the [Method Calls](http://yorick-influxdb.gitlap.com/dashboard/db/method-calls) dashboard:
![method_timings](/uploads/9b431dded22e407401b90ff5d70b27f9/method_timings.png)
This particular method appears to take up quite some time as per the [Method Calls](http://yorick-influxdb.gitlap.com/dashboard/db/method-calls) dashboard:
![method_timings](/uploads/9b431dded22e407401b90ff5d70b27f9/method_timings.png)
https://gitlab.com/gitlab-org/gitlab/-/issues/213After !123, is LDAP Reset service necessary?2019-11-06T04:21:19ZDrew BlessingAfter !123, is LDAP Reset service necessary?Assuming !123 gets merged, is the LDAP Reset service still necessary? The reset service sets all group member access level to Guest and then triggers a sync to re-assign proper level. Now, we downgrade if LDAP says we should.
cc/ @Dou...Assuming !123 gets merged, is the LDAP Reset service still necessary? The reset service sets all group member access level to Guest and then triggers a sync to re-assign proper level. Now, we downgrade if LDAP says we should.
cc/ @DouweM @dzaporozhets https://gitlab.com/gitlab-org/gitlab/-/issues/14907Problems with external Wiki2023-03-21T20:38:38ZAndreas NeumannProblems with external WikiWhen using the function "external Wiki" (in Services) there are options for triggers. But there is a little problem: i have found no documentation what URL is triggered. If it is the only URL given, then the problem appears, that the lin...When using the function "external Wiki" (in Services) there are options for triggers. But there is a little problem: i have found no documentation what URL is triggered. If it is the only URL given, then the problem appears, that the link on the sidebar would point to the same link and would just do for example an "update".
In second there is a problem with triggering a URL when I click on the button "Test Settings" the only URL is triggered and the URL returns a 200, but at the top of the page an error appears "We tried to send a request to the provided URL but an error occurred".
This way two questions appear:
1. How can I distinguish between triggers and users who want to view the external Wiki?
2. What should be the answer of the wiki server to the request, so the error disappears
PS: I know it can be solved with CI and disable all triggers but I don't think that is the target of the Service Developerhttps://gitlab.com/gitlab-org/gitlab/-/issues/14912Have a way to configure the default set of labels (per user)2022-05-19T17:06:48Zxd1leHave a way to configure the default set of labels (per user)Of course labels can differ a lot across projects. However, I suppose individuals usually have a default set of general labels that they are accustomed to across their own projects. For example, when I create a new project, and go to the...Of course labels can differ a lot across projects. However, I suppose individuals usually have a default set of general labels that they are accustomed to across their own projects. For example, when I create a new project, and go to the labels page for it, I want to be able to click on that "generate default labels" button to automatically create ones that I have configured myself. This would save a lot of time for me, compared to having to create all my labels again for each new project.
Of course, then I can continue to edit the labels as appropriate for the particular project itself. But the point is that it will save a lot more time being able to start with a default set one already prefers.
I'm thinking something like having some option to do this possibly in the "Preferences" section of one's "Profile Settings"?https://gitlab.com/gitlab-org/gitlab/-/issues/14917Trello issues importer2024-03-19T17:32:03ZJob van der VoortTrello issues importerIt would be great if we would have an importer that imports issues from a Trello board into a projects issues. It would:
- Create a milestone for each list
- Create an issue for each card
- Set the milestone to the issue accordingly
I ...It would be great if we would have an importer that imports issues from a Trello board into a projects issues. It would:
- Create a milestone for each list
- Create an issue for each card
- Set the milestone to the issue accordingly
I think this would be a great minimal implementation.
cc @dzaporozhets @sytsesBackloghttps://gitlab.com/gitlab-org/gitlab/-/issues/14973Update documentation for unicorn worker defaults2023-08-01T16:18:46ZKelvin MutumaUpdate documentation for unicorn worker defaultsMR for this is being worked on in https://dev.gitlab.org/gitlab/gitlabhq/merge_requests/1883
cc/ @jacobvosmaer @sytsesMR for this is being worked on in https://dev.gitlab.org/gitlab/gitlabhq/merge_requests/1883
cc/ @jacobvosmaer @sytsesBackloghttps://gitlab.com/gitlab-org/gitlab/-/issues/14974SAML Auth (on 8.4 CE Omnibus) leads to 'Retry later' error2023-10-16T21:04:00ZRichard FlemingSAML Auth (on 8.4 CE Omnibus) leads to 'Retry later' errorGreetings,
I'm trying to set up SAML on GitLab (CE 8.4 Omnibus), and after entering credentials on the SAML/SSO logon page, the browser reloads several times (with different SAMLRequest values) and eventually dies at a plain screen read...Greetings,
I'm trying to set up SAML on GitLab (CE 8.4 Omnibus), and after entering credentials on the SAML/SSO logon page, the browser reloads several times (with different SAMLRequest values) and eventually dies at a plain screen reading 'Retry later'
Digging into the logs, gitlab-rails/production.log shows many of the following
Started POST "/users/auth/saml" for 127.0.0.1 at 2016-01-25 11:49:07 -0500
Processing by OmniAuth::RequestForgeryProtection::Controller#index as HTML
Parameters: {"SAMLResponse"=>"..."}
Completed 200 OK in 0ms (ActiveRecord: 0.0ms)
While nginx/gitlab_access.log shows nine POST messages to /users/auth/saml from the SAML server, with the 302 redirect followed by the last POST with a 429 'too many requests' error. That's when I see the 'Retry later' message.
I've seen on the web others talking about clock drift and setting 'allowed_clock_drift' in the saml config part of gitlab.rb, but even setting it to an insane 10800 seconds, I still receive this error.
I've verified that the posted SAML Response is correct, and am now out of options.
One other thing that should be noted. In embedded/service/gitlab-rails/lib/omni_auth/request_forgery_protection.rb I added skip_before_action :verify_authenticity_token as I was getting CSRF token authenticity problems and a 422 message. The SAML server I am using is on another segment of the WAN and it goes through a reverse proxy somewhere. I trust it implicitly however as it's internal.
Any ideas, thoughts, comments would be greatly appreciated!
Cheers!
Richhttps://gitlab.com/gitlab-org/gitlab/-/issues/14975Sync project labels with admin area's labels2022-12-14T18:54:23ZMarkus DoitsSync project labels with admin area's labelsI've all my preferred labels in the admin area of gitlab (let's call them **default labels**). Afaik they will get used when a new project is created. But how can I apply them to existing projects? Now, if I want to have a new label in s...I've all my preferred labels in the admin area of gitlab (let's call them **default labels**). Afaik they will get used when a new project is created. But how can I apply them to existing projects? Now, if I want to have a new label in several of my projects, I have to go to each one and add them one by one - or am I overseeing something?
Basically I want to add and remove labels for multiple projects without going through each one.
To make this much easier a project setting would be nice to always use default labels. If it is checked, at least those default labels are available in the project. One can of course create more project labels for this one project, but the default labels are fixed. So I propose:
- Create a new project setting/checkbox `Use default labels` (or similar)
- If checked, all default labels are always available in that project
- New project labels can still be created and removed for that one project
- If a new label is added as a default label, it is available in those projects with `Use default labels` checked
- If an existing label is removed from default labels or the setting `Use default labels` is getting unchecked:
- if the project has an issue tagged with that default label, the label is converted to a project label
- if the project never used this label, the label is simply gone
- If a new default label is created or the setting is getting checked for an existing project:
- ~~if there is already a project label with the same name as a default label, it is replaced by the default label (so the color might change)~~ might be better to use the project label's color instead, so a default label never overwrites a project label (to keep the project fully customizable, even with some default labels)
Is this a viable approach for label management?Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/14976Allow configuring GitLab runner priority2024-01-30T02:31:17ZDaniel BrooksAllow configuring GitLab runner priority## Status update (2023-08-03)
- We have not determined a path forward to address the pain points described in this issue.
- After a few customer interviews starting the week of 2023-07-24, I have created an [issue](https://gitlab.com/g...## Status update (2023-08-03)
- We have not determined a path forward to address the pain points described in this issue.
- After a few customer interviews starting the week of 2023-07-24, I have created an [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/419985) aimed at developing a proof-of-concept solution.
## Problem to solve
I have multiple runners for a project which run on very different machines, some slow (my dev machine), some fast (build server). I'd like to prioritize the runners, so that gitlab always tries to use the runners in a certain order, in my case: use the fasted idle/available runner possible. So I would always the the shortest build times.
## Proposal
It would be great to see the ability to define runner priority orders in the gitlab runner interface.
For instance, you could have multiple runners with the tag ios, but if a certain runner is available you want it to run on that one first. This could be because that runner has better hardware and the others are there as spares, but the first one can run the build faster.
### Possible MVC implementations:
- Allow multiple [runner tags](https://docs.gitlab.com/ee/ci/yaml/#tags) to indicate priority of the runners to be used. eg; if tag 1 is unavailable default to tag 2, tag 3, etc.
### Possible Future UI implementations:
- a switch on the runners page to select between (old)round robin and (new) prioritized
- drag and drop the runners into a certain order, when in prioritized mode
## Implementation notes
- Such a change will require changes in rails
- This proposal will increase the - already huge - complexity of the SQL queries that are powering jobs scheduling. We may have to get back to the idea of a `CI Daemon` that would handle scheduling and therefore not relying on the DB.Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/234Unable to auto merge on successful build using Jenkins CI2023-10-08T11:19:07ZjejUnable to auto merge on successful build using Jenkins CII have repos configured via the Jenkins CI service to trigger builds when a merge request is created. If I select the "Merge when build succeeds" option after creating the merge request, the merge request remains in a state where it's in...I have repos configured via the Jenkins CI service to trigger builds when a merge request is created. If I select the "Merge when build succeeds" option after creating the merge request, the merge request remains in a state where it's indefinitely waiting on a successful build result. While it's stuck in this state, Jenkins has already returned a successful result but the state of the merge request remains unchanged.
![auto_merge](/uploads/2f5f2c0b5d562f49146c61809e2b224e/auto_merge.png)
I can't tell if it's a issue on the Gitlab side or the Jenkins Gitlab plugin side. I am using Gitlab 8.3.4 with Jenkins Gitlab plugin 1.1.28. I followed the instructions here for setup: http://doc.gitlab.com/ee/integration/jenkins.htmlhttps://gitlab.com/gitlab-org/gitlab/-/issues/240Feature Proposal: Allow pulling issues and pull requests for project being pu...2019-11-06T04:21:11ZBartosz OudekerkFeature Proposal: Allow pulling issues and pull requests for project being pushed to GitHub.Issue gitlab-org/gitlab-ee#116 is planned to be included in 8.6. I suspect many projects will use it to push their code to GitHub, like GitLab itself is already doing. I think one great feature would be (if at all possible) to allow pull...Issue gitlab-org/gitlab-ee#116 is planned to be included in 8.6. I suspect many projects will use it to push their code to GitHub, like GitLab itself is already doing. I think one great feature would be (if at all possible) to allow pull requests, and possibly issues, to be imported at the same time, like is currently possible when creating a project.https://gitlab.com/gitlab-org/gitlab/-/issues/14989Make label view filterable2022-05-19T17:06:50ZJob van der VoortMake label view filterableWith JS.With JS.https://gitlab.com/gitlab-org/gitlab/-/issues/14995Allow users to set Wiki as default project view2024-03-25T02:02:51ZprobablypatAllow users to set Wiki as default project view#### ~"type::feature" Description
Feature Request for a Wiki to be enabled as the default project view. Right now we are using projects as wiki's but it requires the user to choose the project then select the view the wiki.
#### This i...#### ~"type::feature" Description
Feature Request for a Wiki to be enabled as the default project view. Right now we are using projects as wiki's but it requires the user to choose the project then select the view the wiki.
#### This is a two part request:
* [x] Customers want the capacity to allow Wiki as the default Project view on a granular user/user basis.
* [ ] Customers want the capacity for a Project admin to enable the Wiki as the default view.
#### Update 2023-05-30:
We've accomplished part 1 of this request via https://gitlab.com/gitlab-org/gitlab/-/merge_requests/116276+. Part 2 remains TBD.Johannes BittnerJohannes Bittner