@claude - Let's update the Mattermost Product Documentation to note that plugin developers can now configure Interactive Dialog datetime fields with timezone-aware display and manual time entry from Mattermost server v11.6.0 onward captured via Engineering PR #34932.
Scope & constraints:
- Review PR #34932 as the source of truth.
- Do not modify changelogs, important upgrade notes, version archive, removed/deprecated feature docs, or unsupported legacy release docs.
- Keep this to ONE task focused on the integrator/developer capability change, not multiple persona sections.
- Do not document implementation details such as internal structs, utility refactors, Moment handling, or test coverage unless directly needed to explain the user-facing config surface.
Required doc touchpoints:
- Update the Interactive Dialog / plugin developer documentation in the Mattermost developer docs.
- Identify the exact page covering Interactive Dialog field parameters and datetime field behavior.
- Add the new datetime configuration options and behavior notes there rather than creating a new page.
Output requirements:
Return:
- the exact page(s) to update,
- the proposed before/after text,
- a short rationale for placement,
- confirmation that the version reference uses Mattermost server v11.6.0 based on PR milestone evidence.
The proposed text should minimally document:
- that datetime dialog fields can display in a specified IANA timezone,
- that datetime dialog fields can allow manual time entry,
- that manual entry accepts exact typed times rather than only dropdown interval selection,
- any user-visible behavior that is necessary for correct integrator understanding, such as timezone indicator/display expectations.
Keep the wording capability-focused and concise.
@claude - Let's update the Mattermost Product Documentation to note that plugin developers can now configure Interactive Dialog datetime fields with timezone-aware display and manual time entry from Mattermost server v11.6.0 onward captured via Engineering PR #34932.
Scope & constraints:
Required doc touchpoints:
Output requirements:
Return:
The proposed text should minimally document:
Keep the wording capability-focused and concise.