Skip to content

reword the dormant template notification #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
BrunoQuaresma opened this issue Jul 25, 2024 · 0 comments · Fixed by coder/coder#14029
Closed

reword the dormant template notification #25

BrunoQuaresma opened this issue Jul 25, 2024 · 0 comments · Fixed by coder/coder#14029
Assignees
Labels
docs Improvements or additions to documentation project/notifications

Comments

@BrunoQuaresma
Copy link

From coder/coder#13868 (comment)

The wording is a little weird here. Can we change it and add a link to the dormancy docs:

I don't think we need to include the initiator, just improve the reasons (see end of message).

Hi {user-name}, your workspace {ws-name} has been marked dormant because of {reason}.

Append if dormancy cleanup is enabled and dormancy_hours < 24:

Dormant workspaces are automatically deleted after {dormancy_hours} hours of inactivity.

Append if dormancy cleanup is enabled, and dormancy_hours > 24:

Dormant workspaces are automatically deleted after {dormancy_hours // 24} days of inactivity.

To prevent deletion, use your workspace with the link below.


The reasons also fit into differing grammatic context:

  • Lifecycle executor: "breached the template's threshold for inactivity"
  • API: "requested by user"
  • Template: "template updated to new dormancy policy"

If we use these, they'd fit the above messages better.

  • Lifcycle: "prolonged inactivity, exceeding the dormancy threshold"
  • API: "a user request"
  • Template: "an update to the template's dormancy"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation project/notifications
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant