Configuring Service Desk
-
Has anyone configured GitLab to do service desk? Looks like it just needs some email configuration done to the yml files but not quite sure where to start. Reading the Gitlab help pages indicates I need to se up email for inbound mail processing. Would the CR app not already have done that?
-
Has anyone configured GitLab to do service desk? Looks like it just needs some email configuration done to the yml files but not quite sure where to start. Reading the Gitlab help pages indicates I need to se up email for inbound mail processing. Would the CR app not already have done that?
-
@doodlemania2 Currently, incoming email is not automated in the package. I am working on an update for that.
I don't know if that will help the Service Desk feature though.
-
@girish nice! just didn't want to start down that rabbit hole if it was already in there somewhere and broke it
@doodlemania2 The latest package supports incoming email. Service desk also works after that - https://docs.cloudron.io/apps/gitlab/#incoming-email
-
@doodlemania2 The latest package supports incoming email. Service desk also works after that - https://docs.cloudron.io/apps/gitlab/#incoming-email
-
@girish that's amazing - QQ though - I don't have the feature in the Email tab like it describes in the docs:
vs me:
Am on 7.0.4 and inbound mail is configured:
@doodlemania2 this doesn't really help, but I can confirm that those Email options are there on a fresh install.
If there isn't an easier way I guess you could clone your existing app into a new one? (or perhaps that is the easier way?!?)
-
@doodlemania2 this doesn't really help, but I can confirm that those Email options are there on a fresh install.
If there isn't an easier way I guess you could clone your existing app into a new one? (or perhaps that is the easier way?!?)
@jdaviescoates i'm not above blowing away my existing install if that's what it takes!
-
@jdaviescoates i'm not above blowing away my existing install if that's what it takes!
@doodlemania2 before you blow it away, I wonder why it's not being shown. Can you confirm the package version is v1.58.1 ? Looking at the code, the UI should show itself for
app.manifest.addons.recvmail, so it's either the GitLab package is not the latest one (I only added this couple of releases ago) OR maybe can you refresh your browser just to be doubly sure ? -
@doodlemania2 before you blow it away, I wonder why it's not being shown. Can you confirm the package version is v1.58.1 ? Looking at the code, the UI should show itself for
app.manifest.addons.recvmail, so it's either the GitLab package is not the latest one (I only added this couple of releases ago) OR maybe can you refresh your browser just to be doubly sure ?@girish
Sad me, I blew it away about 5 minutes ago - I am seeing it now though!
Now, I'm not sure what to plug in to the config section:
Is address
git@apps.thedoodleproject.netand user/password my credentials or did a service account of sorts get created or ? -
@girish
Sad me, I blew it away about 5 minutes ago - I am seeing it now though!
Now, I'm not sure what to plug in to the config section:
Is address
git@apps.thedoodleproject.netand user/password my credentials or did a service account of sorts get created or ?@doodlemania2 Did you create a mailbox named
git@already ? After you have done that, I would first test if incoming email integration works is general. For example, create a test project and see if you can mail in issues. You can then enable service desk in that project and you can mail in service desk requests as well. This should all work out of the box.You need the "custom address" for Service Desk only if you don't want "git@" for the Service Desk but something else like "helpme@" or something. For the latter case, you have to create a mailbox named "helpme@" and then put the password of that mailbox into the configuration.
-
@doodlemania2 Did you create a mailbox named
git@already ? After you have done that, I would first test if incoming email integration works is general. For example, create a test project and see if you can mail in issues. You can then enable service desk in that project and you can mail in service desk requests as well. This should all work out of the box.You need the "custom address" for Service Desk only if you don't want "git@" for the Service Desk but something else like "helpme@" or something. For the latter case, you have to create a mailbox named "helpme@" and then put the password of that mailbox into the configuration.
@girish Got it! Now that I read the instructions more clearly, it makes sense.
Now - when I send a message to my "private" issue repo (git+derek-test1-2-dmpv512f9bq1v22fe7mehyc4x-issue@mydomain.com) it lands in my catch all address bucket and not in Gitlab.
Do I need to unconfigured catch-all?
-
@girish Got it! Now that I read the instructions more clearly, it makes sense.
Now - when I send a message to my "private" issue repo (git+derek-test1-2-dmpv512f9bq1v22fe7mehyc4x-issue@mydomain.com) it lands in my catch all address bucket and not in Gitlab.
Do I need to unconfigured catch-all?
-
@doodlemania2 can you see if the mail room service is running by
supervisorctl statusin the Web terminal ? Also, can you check if there are any errors in the logs? -
@girish
That could be the situation! Let me try to bounce it and try again. -
@girish - looks like the service bounces:
-
@doodlemania2 From the Web Terminal, does
telnet mail 9393work? If not, can you check if the mail server is running in Services? Maybe give it a restart and see if it helps? -
@girish yep sure does!
@doodlemania2 there is that thing about /home/git not being writable - didn't know if that was related to the email address being git@ (shrug)
-
@doodlemania2 there is that thing about /home/git not being writable - didn't know if that was related to the email address being git@ (shrug)
-
@doodlemania2 just to double check, did you create a mailbox named
git@in Email -> Domain -> Mailboxes ? This is not created automatically. -
@girish doink - THAT did it!
