Skip to content
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

Slack improvement requirements #2302

Closed
6 tasks done
JanCizmar opened this issue May 13, 2024 · 1 comment
Closed
6 tasks done

Slack improvement requirements #2302

JanCizmar opened this issue May 13, 2024 · 1 comment
Assignees

Comments

@JanCizmar
Copy link
Contributor

JanCizmar commented May 13, 2024

  • When user with connected account modifies data the username should be replaced with tag in slack (@)
    image
    admin@admin.com should be replaced with @Jan Cizmar, since my slack account is connected

  • A space is missing between the user name and 'has'

  • Change the color or the user name too (pink-red or bold)

  • The "Open in Tolgee" button is should not have padding

  • Pls. delete button contact support and add documentation link
    image

  • Add message about change in small font (user, event, time)
    image

@JanCizmar
Copy link
Contributor Author

JanCizmar commented May 13, 2024

Personas and use cases

1. PMs (Project Manager / Product manager / UX designer)

  • Want to be notified about new keys base languages wording
  • Not necessarily want to know other languages wording
  • Want to know translation state of the other languages (to know if all the strings are translated)
  • Want to know, who is active (translators reviewers) in the project
  • We can expect this persona will be able to scroll to see if everything is translated / green
    • That means merging makes perfect sense here
    • We want to prevent spamming new notification about every single language change

2. Translators

  • Want to be notified about new keys created / base language values changed
  • Comments (out of scope yet)

3. Reviewers

  • Want to be notified about changes in a selected language
  • They're not interested in new key creations nor base language updates (unless they're reviewers of the base language)
  • Comments (out of scope yet)

Conclusion

  • By default /tolgee subscribe <projectId> command I would notify only about the events relevant for 1. PMs and 2. Translators. While I would group the other (non-base) languages modifications to the key creation / base language change notification.
  • I would never group other events the other language changes. So key creation o base language change change would never be grouped.
  • I would add information about the time and autor of last change to subsequent language change
  • Even if the modification on key wasn't grouped I would still update past messages. (With some max message count (200?))
  • I would enable 3. Reviewers personas preventing grouping of subsequent modifications by subscribing to specific languages. E.g., if they explicitly subscribe to Czech, the Czech update would never be grouped, so they're still notified about new changes.

@ZuzanaOdstrcilova what do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants