vipul-sharma20 / slate Goto Github PK

Is your feature request related to a problem? Please describe.
If there are multiple team's standup configured in the same channel, it'll be difficult to distinguish among standup submissions when they are published.

Currently, the message is: "Daily Standup Complete" and then the thread of team's submission.

Describe the solution you'd like
Can embed team name in the message for eg: "Daily Standup Complete for team."

This will make it easier for people to get started with their self hosted app.

Make a more readable format for submissions. Refer to Slack's block kit builder: https://app.slack.com/block-kit-builder

Jacked from something a colleague shared earlier.

Updating publish time always writes as 13:00. Bug here: https://github.com/vipul-sharma20/slack-standup/blob/master/app/handlers.py#L45

Standup does not work for people who are part of multiple teams. The application will not allow submission as the standup submission would already exist for user.

Additionally, the reporting mechanism has to be changed. Currently, submission logic picks up user's current day's submission (without checking the team).

Want to able to access standup info, so secondary places (like outline) could also ingest the standup logs.

Update postman collection requests, examples and documentation

The bot creates a new channel message if a new standup post is made by someone after the usual standup is published.

Describe the solution you'd like
Make the bot reply in the same old thread where is posted the rest of the standup entries.

Describe alternatives you've considered

Additional context
@vipul-sharma20 himself said:

I would need to store the thread id so it replies to the thread and not as a new message. I have not stored the thread id yet so it posts as a new message.

Is your feature request related to a problem? Please describe.
Deployment has to maintain crontabs for notification/publishing in a different place than main application.

Describe the solution you'd like
App backend should be able to handle all the scheduled actions instead of maintaining crons.

Is your feature request related to a problem? Please describe.
Missing easy deployment steps on a k8s cluster.

Describe the solution you'd like
A helm chart or manifests which could be used to set it up on a k8s cluster

This will help with any configuration we would want to do for people in a specific team.

Custom standups for each team should also be noted while adding this feature.

Describe the bug
A clear and concise description of what the bug is.
The "Didn't hear from..." mentions lists out the users who haven't submitted their standup. But after they do, this list should get updated to show who are left.

Solutions:

1. Update the original "Didn't hear from..." message
2. Mention users who submitted late as a reply in the thread

Add existing responses to standup questions in the modal if user opens the dialog after the standup submission

Standup submission is only visible at the time standup is published on the channel. All users should get a copy of their submission as DM after submission.

I try to create new standup via /standup command and get only message: No user details or standup exists for this request. Your user details or standup for your user/team doesn't exist in the database.

What am i doing wrong?

Describe the solution you'd like
Helm release action leverage gh-pages to include the index.yaml on the self hosted.

The Trino folks run a similar setup to this repo, seen here.

It just makes it easier to do:

helm repo add trino https://trinodb.github.io/charts/
helm install my-trino trino/trino --version 0.2.0

Publish user submissions as threaded messages. Add a customizable config to publish as top post or threaded.