When I try to link a gitlab issue it will fail due to this subfolder. I assume that the group and project parameters get parsed from the URL ignoring the subfolder in the endpoint configuration in the integration settings. When I remove the subfolder in the link the process succeeds but the link to the issue will be broken.
Is there a fault at my side? Do I overlook something? If not I think this issue can be resolved by adding a “directory” configuration in the Gitlab integration settings panel or by parsing the directory from the endpoint.
Thanks in advance!
Expected behavior:
After setting up GitLab Integration adding a link to a issue on this GitLab Instance should create a link in the ticket ignoring the root folder.
Actual behavior:
Pasting the link of the gitlab issue into the ticket will fail with “Loading of issues not possible” because the URL contains a subfolder e.g.
Can you please point me to the official documentation page that handles the support of the usage of subdirectories? I wasn’t able to find the official documentation page for it.
Due to the fact that it does not metion anything about location requirements for the gitlab installation it did not work for me by following these instructions.
It does not work as intended so I wrote in this forum. Is there anything incorrect? I just suggested correcting the behaviour what you do with this suggestion is on your side.
First of all, this is not an issue tracker.
It’s a forum for technical questions etc.
Which is why I’ve been asking for you to provide a documentation URL for GitLab that shows how to configure GitLab on subdirectories.
The reason I am asking is quite simple:
If this is not supported by the original vendor software, it’s not supported by us as well. We’re looking for specific URL patterns. In order to have any close chance of reproducing and doing it “right”, I’m in need of requested documentation.
If this is not officially supported you cannot expect it to work.
If it’s not official supported by the vendor, I also don’t see a reason why we should add this to the documentation as it expects default / supported methods.
Thank you for stating the reason, so I can work with that as well.
In my prevous response I thoght you were talking about the documentation of Zammad not Gitlab so that brough confusion on my side.
Here is the official GitLab documentation regarding this issue:
I can confirm this slightly odd behavior.
It doesn’t seem to be related to the regular expression as I expected:
It’s getting interesting if I fiddle with the URLs.
I’m not sure if this is a direct Zammad related issue, one would have to check that against the API to double tab. Links of course don’t work in that scenario and thus the function get’s broken to half.
The odd behavior based on the URL makes me unsure on which side the issue lives.
@rolfschmidt could you possibly have a look? If you need help reproducing let me know next week I’ll spin a fitting instance for you.
