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

(investigate) Updating already sent slack messages #260

Closed
krzysztofrewak opened this issue Nov 29, 2022 · 0 comments · Fixed by #300
Closed

(investigate) Updating already sent slack messages #260

krzysztofrewak opened this issue Nov 29, 2022 · 0 comments · Fixed by #300
Labels
backend backend feature feature new feature to implement investigation things to research

Comments

@krzysztofrewak
Copy link
Member

I think this task is doable, but we there is some investigation needed.

Example from today: a few people clicked "working from home" in Toby before 0800, but one person clicked it after that. Because that the slack message is outdated:
image
image


I know that slack messages can be updated, because I saw it with Github notifications:
image

In example above a slack message appears and few seconds later asingees or labels are appearing.

Could we update our list everyday?

@krzysztofrewak krzysztofrewak added feature new feature to implement investigation things to research backend backend feature labels Nov 29, 2022
Baakoma added a commit that referenced this issue Apr 20, 2023
Baakoma added a commit that referenced this issue May 25, 2023
* #260 - update already sent summaries

* fix

* fix deploy

* - fix

* fix deploy - login to the server

* fix deploy - login to the server

* fix deploy - git identity on the server

---------

Co-authored-by: Marcin Tracz <[email protected]>
Co-authored-by: EwelinaLasowy <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend backend feature feature new feature to implement investigation things to research
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants