Update project notification settings
Absent fields are left alone. Digests already queued move to the new schedule.
Who may call it: Whoever manages the project: an owner, security admin or admin of its organization, or an admin of the project. API keys: no.
sessiongamma.session_token<token>The session cookie a sign-in sets. Over HTTPS its name carries the __Secure- prefix. Browsers send it on their own; other clients keep it from the sign-in response.
projectId*stringThe project's id.
application/json- body
frequencies?By notification type; the types left out keep theirs.
hour?integerThe hour digests go out, local to timeZone.
0 <= value <= 23weekday?integerThe day weekly digests go out; 0 is Sunday.
0 <= value <= 6timeZone?stringAn IANA zone.
OK.
application/json- response
types*array<>Every type a member can hear about, in the page's order.
hour*integerThe hour digests go out, local to timeZone.
0 <= value <= 23weekday*integerThe day weekly digests go out; 0 is Sunday.
0 <= value <= 6timeZone*stringIANA zone, for members who have not set their own. UTC by default.
curl -X PUT 'http://localhost:3000/api/projects/string/notification-settings' \ -H 'Content-Type: application/json' \ -d '{}'{ "types": [ { "type": "issue.assigned", "group": "string", "label": "string", "description": "string", "frequency": "instant" } ], "hour": 0, "weekday": 0, "timeZone": "string"}