GItlab does not send email on new issue, but do it for issue closing and comments. How can I enable it?
Any notification rule issue on GitLab are referenced ("featured") in Issue 2669.
A redesign is in progress (issue 1808), but not there yet.
Proposals already exists (issue 2466, issue 1448 ), where you can select the people in a team you want to be notified:
That feature request is managed here: "Improve email/notification system".
Related
It's been known for a while that LightShot has privacy issues as discussed here
but most articles discussing the technicalities mention only about the Upload, Save, or Share.
Will clicking only on the COPY button still expose me to data / screen-scrapers?
I tried mailing LightShot, but I don't think I'll get a response since mailer daemon replied with a full inbox status.
I found issue in JvDesktopAlertStack,but cannot create account in https://issuetracker.delphi-jedi.org/signup_page.php (create but confirm email not received).
How can report this issue?
procedure TJvDesktopAlertStack.UpdatePositions
ignore dapMainFormBottomRight,dapMainFormBottomLeft etc,specifically
on MultiMonitor.
I'll have a look at the email issue, but in the meantime, could you create a test application as a GIST?
Or even better, if you have a suggested fix, create a pull request at github.
I'm building a Telegram bot for myself that should send to me notifications when I get any. I'm trying to achieve the same behavior as GitHub's email notifications. The problem is that I'm not sure if it's even possible. I'm working with GitHub API for few days straight trying to solve this issue but I still have no idea how to do it. It's like GitHub API doesn't provide enough information about the notification.
For example, it provides field "reason", which describes why I got this notification but how to understand what this notification is about? Like, if I was assigned to the issue or pull request (right now it seems like notifications are the same whether I got assigned to the issue or got a new message in the assigned issue), or got a new message in a watching issue/pull request or anything else.
I've changed my notification setting on gitlab to On Mention, but I don't receive any emails when I'm assigned an issue. Is this a limitation of the On Mention email scope, or is there another setting I can change in order to receive these emails?
Thanks
With the On mention settings, you only receive emails when you are mentioned in a comment, specifically using the #username syntax.
For your needs, I suggest switching to the Participating notification level.
Can anyone help.
I’m using the rest api to create an envelope, and then configure it using the api sender view call (/restapi/v2/accounts//envelopes//views/sender) to get the DocuSign UI.
Creating the envelope and viewing it the first time using sender view to bring up the docusign api works fine.
The problem occurs if instead of sending the envelope I click ‘save as draft’. When I try to go back to the envelope and view it again using sender view I get the following error with http status of 400:
{
"errorCode": "EDIT_LOCK_ENVELOPE_LOCKED",
"message": "The envelope is locked. The lock must be released before requesting the sender token for envelope, id = xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx."
}
The lock seems to wear off after time (apprx 20 mins). However after it wears off I can only view the item once, and then the lock is reapplied.
I can’t find anything in DocuSign api documentation that relates to this behaviour. Any help would be appreciated.
UPDATE (12/Feb/15): This error only happens on my demo account but not on production, so it seems like it's an account setting, but I can't figure out what/where the setting is.
Thanks,
Nick
Yes - there is new documentation about this envelope locking feature and behavior in the February service pack (PDF) available here: https://www.docusign.com/support/releases.
We have a bug logged on our side where Save Draft isn't correctly releasing the lock on the envelope. We should have a fix for this issue in our DEMO environment soon. The locking feature is currently only "ON" in our DEMO environment but not in our Production environments while we find and fix potential issues such as the one identified here. More information about locking is in our February service pack (PDF) release notes available here: https://www.docusign.com/support/releases.