Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

api-changelog: Clarify feature level 162 descriptive text. 

Original API changelog entries: commit 73f0eae394 and
commit 2c4e076fef and commit 891f83601d.
This commit is contained in:
Lauryn Menard 2023-05-22 17:59:24 +02:00 committed by Tim Abbott
parent 0e9c34a975
commit e4ae8b79c3
2 changed files with 49 additions and 42 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
api_docs/changelog.md
View File

@ -209,16 +209,16 @@ format used by the Zulip server that they are interacting with.
**Feature level 162**
* [`POST /register`](/api/register-queue), [`GET /events`](/api/get-events),
`PATCH /realm`: Added new `move_messages_within_stream_limit_seconds` setting.
* [`POST /register`](/api/register-queue), [`GET /events`](/api/get-events),
`PATCH /realm`: Added new `move_messages_between_streams_limit_seconds` setting.
* [`PATCH /messages/{message_id}`](/api/update-message): Time limit to edit
topics, for users other than administrators and moderators, can now be
configured using `move_messages_within_stream_limit_seconds` setting.
* [`PATCH /messages/{message_id}`](/api/update-message): Time limit to move
messages between streams, for users other than administrators and moderators,
can now be configured using `move_messages_between_streams_limit_seconds` setting.
* `PATCH /realm`, [`POST /register`](/api/register-queue),
[`GET /events`](/api/get-events): Added two new realm settings
`move_messages_within_stream_limit_seconds` and
`move_messages_between_streams_limit_seconds` for organizations to
configure time limits for editing topics and moving messages between streams.
* [`PATCH /messages/{message_id}`](/api/update-message): For users other than
administrators and moderators, the time limit for editing topics is now
controlled via the realm setting `move_messages_within_stream_limit_seconds`
and the time limit for moving messages between streams is now controlled by
the realm setting `move_messages_between_streams_limit_seconds`.
**Feature level 161**

71
zerver/openapi/zulip.yaml
View File

@ -4071,29 +4071,31 @@ paths:
nullable: true
description: |
Messages sent more than this many seconds ago cannot be moved within a
stream by members with this organization's [message move
policy](/help/restrict-moving-messages). This setting does not
affect moderators and administrators.
stream to another topic by users who have permission to do so based on this
organization's [topic edit policy](/help/restrict-moving-messages). This
setting does not affect moderators and administrators.
Will not be 0. A `null` value means no limit: messages can be moved
regardless of how long ago they were sent.
Will not be 0. A `null` value means no limit, so message topics can be
edited regardless of how long ago they were sent.
**Changes**: New in Zulip 7.0 (feature level 162). Previously, this
limit was always 72 hours.
**Changes**: New in Zulip 7.0 (feature level 162). Previously, this time
limit was always 72 hours for users who were not administrators or
moderators.
move_messages_between_streams_limit_seconds:
type: integer
nullable: true
description: |
Messages sent more than this many seconds ago cannot be moved between
streams by members with this organization's [message move
policy](/help/restrict-moving-messages). This setting does not
affect moderators and administrators.
streams by users who have permission to do so based on this organization's
[message move policy](/help/restrict-moving-messages). This setting does
not affect moderators and administrators.
Will not be 0. A `null` value means no limit: messages can be moved
Will not be 0. A `null` value means no limit, so messages can be moved
regardless of how long ago they were sent.
**Changes**: New in Zulip 7.0 (feature level 162). Previously, it
was not possible to add a time limit for moving messages.
**Changes**: New in Zulip 7.0 (feature level 162). Previously, there was
no time limit for moving messages between streams for users with permission
to do so.
move_messages_between_streams_policy:
type: integer
description: |
@ -6918,12 +6920,15 @@ paths:
administrators or moderators, try to move messages after these time
limits have passed.
Before Zulip 7.0 (feature level 162), users who were not
administrators or moderators could only edit topics if the target
message was sent within the last 3 days. That time limit is now
controlled by the `move_messages_within_stream_limit_seconds` setting. A
similar time limit for moving topics to different streams was added,
controlled by the `move_messages_between_streams_limit_seconds` setting.
Before Zulip 7.0 (feature level 162), users who were not administrators or
moderators could only edit topics if the target message was sent within the
last 3 days. As of this feature level, that time limit is now controlled by
the realm setting `move_messages_within_stream_limit_seconds`. Also at this
feature level, a similar time limit for moving messages between streams was
added, controlled by the realm setting
`move_messages_between_streams_limit_seconds`. Previously, all users who
had permission to move messages between streams did not have any time limit
restrictions when doing so.
Before Zulip 7.0 (feature level 159), editing
streams and topics of messages was forbidden if
@ -12952,15 +12957,16 @@ paths:
Present if `realm` is present in `fetch_event_types`.
Messages sent more than this many seconds ago cannot be moved within a
stream by members with this organization's [message move
policy](/help/restrict-moving-messages). This setting does not
affect moderators and administrators.
stream to another topic by users who have permission to do so based on this
organization's [topic edit policy](/help/restrict-moving-messages). This
setting does not affect moderators and administrators.
Will not be 0. A `null` value means no limit: messages can be moved
regardless of how long ago they were sent.
Will not be 0. A `null` value means no limit, so message topics can be
edited regardless of how long ago they were sent.
**Changes**: New in Zulip 7.0 (feature level 162). Previously, this
limit was always 72 hours.
**Changes**: New in Zulip 7.0 (feature level 162). Previously, this time
limit was always 72 hours for users who were not administrators or
moderators.
realm_move_messages_between_streams_limit_seconds:
type: integer
nullable: true
@ -12968,15 +12974,16 @@ paths:
Present if `realm` is present in `fetch_event_types`.
Messages sent more than this many seconds ago cannot be moved between
streams by members with this organization's [message move
policy](/help/restrict-moving-messages). This setting does not
affect moderators and administrators.
streams by users who have permission to do so based on this organization's
[message move policy](/help/restrict-moving-messages). This setting does
not affect moderators and administrators.
Will not be 0. A `null` value means no limit: messages can be moved
Will not be 0. A `null` value means no limit, so messages can be moved
regardless of how long ago they were sent.
**Changes**: New in Zulip 7.0 (feature level 162). Previously, it
was not possible to add a time limit for moving messages.
**Changes**: New in Zulip 7.0 (feature level 162). Previously, there was
no time limit for moving messages between streams for users with permission
to do so.
realm_community_topic_editing_limit_seconds:
type: integer
description: |