geodoo / post-your-standup Goto Github PK

Check this: https://docs.github.com/en/enterprise/2.13/user/articles/emoji-on-github-pages

change to https://pages-themes.github.io/hacker/

theme: jekyll-theme-hacker

in the _.config.yml file

If you want to go the extra mile find a way to add authors, like a config parameter in this file. For example, is this relevant: https://jekyllrb.com/docs/step-by-step/09-collections/ ?

https://blog.sorryapp.com/blogging-with-jekyll/2014/02/06/adding-authors-to-your-jekyll-site.html ?

Like how we have the actual Slack app, we need to expose the Apollo server.

Ideally, frontend needs to read from this

When me merge the code back to master ideally we should trigger a deploy to the server!

relevant to: #147

Slack app should not be the front of the website: I would change URL to: https://post-your-standup-api.codinginsights.blog since it is the API let's say of the website

Frontend app should be the website and admin should be for users with credentials https://post-your-standup.codinginsights.blog

Currently, there is no validation to ensure you can post only YOUR standup with your email. If you use other valid JIRA email, it will give you a "false" standup.

Discuss if this is an actual problem and if so, how to fix it

Currently we store user token as is in db. We should use some kind of salt/hash whatever to store them safely

Ideally, we would like to have a Reporting tab or sth similar that logs all errors and meaningful info about them, so we can potentially solve them.

Daily backups and delete after 1 month

Bolt applications by default listen to /slack/events endpoint. From the docs

Further investigation is probably needed in case it is not the case or we need more endpoints (??)

After you log in to the Dashboard Apollo client needs to refresh the token automatically. Now, you need to refresh the page manually.

Current behaviour:

Desired behaviour:

Use probably POSTMAN for development along with ngrok maybe?

In order to make this dynamic as for first release we would like to enable user to choose with project on Jira he wants to post his standup about.

The simplest way to do this is to add it as argument to the command.

sth like:

/standup PROJECT

Try dockerise each app/service, so they can be deployed easily and separately

At the moment we have only the db in docker container. Try add the app itself, the admin apps etc

We ll need to do also two environments: one dev and one prd

We should dockerise the following:

• Frontend app
• Backend API for frontend app
• Slack app

Maybe we can create a frontend or backend Dashboard that shows data analytics and other useful stuff where we can probably login with auth0 accounts and login page

Maybe we can extend the support to other tools like:

• https://trello.com

When we remount especially and previous connection was unsuccessful somehow, then we have to manually delete the data in

~/mongo/standup

volume path

I guess the db to use is also to be decided!!

We need to save several data like the following:

• users
• Jira projects
• Jira board columns (or statuses)
• channels
• other data for validation and authorization etc

Lefteris's idea: make a route to get the install URL (??) from receiver.installer.generateInstallUrl()

check: https://slack.dev/bolt-js/concepts#authenticating-oauth

Currently, we have prod app multi-workspace and dev apps single-workspace. This creates problems when we try to test the prod app installation or stuff that only prod app currently has.

So, we need to make them all multi-workspace and change the docs for contributors. It will require cleanup in app.js and removal of LOCAL_DEV env variable too.

The docs are terrible!!

Make the app dynamically creating the bot token (?)

Try and see if you can make an interactive experience, like the user can choose which tickets worked Yesterday and which tickets will work Today and add also Blockers section.

An example:

_Yesterday:_
 1. Worked on ticket 3098
 2. Worked on ticket 3120
_Today:_
 1. Working on ticket 3302 
_Blockers:_
 1. I am waiting backend to confirm the JSON schema for endpoint /blahblah

create ESlint file to format the code and make suggestions on how to improve it

Maybe check this: https://www.linode.com/docs/quick-answers/websites/how-to-install-certbot-on-ubuntu-18-04/

Check what is the best structure for node projects. Maybe sth like a src/ folder etc?

We need to restrict the Dashboard and maybe future UI pages to specific users etc. Therefore we ll need some kind of user management and login system.

auth0.com can be used (free version)

Maybe check https://github.com/semantic-release/semantic-release

Also, make use of commitizen format maybe: https://github.com/commitizen/cz-cli

As a user I would like to choose which tickets to include/exclude to my standup and to add any blockers, so that I can add only the tickets I want to talk about during my standup

In the future, explore conditional add of Jira tickets and split in two sections: currently doing and blockers.

Maybe user can have a modal to choose from a list of tickets and include/exclude anything he wants, then post actually to the channel.

A simple example is /giphy query where you are presented which 3 buttons and you can send current photo, shuffle or cancel

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

relevant to: #150

Create a landing page with info about the app, like this, for example: https://www.socialintents.com/slack-chat-widget.html

Also, Basecamp's black and white is nice!

Find way to dynamically create the Add to Slack button, maybe with a new get route on the slack app. Check also this: #149

There are a lot of strings floating around the app. It would be nice to put them in constants.

We need to add docs for this new feature: how to run and use it

Unfortunately, we noticed that the issues fetched are not correct. We need to change the command so we get the user's email and check for his issues correctly. Not the authenticated user's only!!

🤦