damiththa/gitkrakenglotodos

gitkrakenglotodos's Issues

Card position

When a recurring task is moved to a CLOSED column, then when is sending back to originating column, it goes in with card column position 0.
This only happens when card is moved to CLOSED column via card detail shortcut. That is becuase, when GLO sends the card that way, it populates the card with position 0 by default.

However, if the card is moved to CLOSED column by dragging and dropping, the card poputes back to the same position

Introducing auth lambda layer

As an enhancement, introduce Auth. lambda layer for verification and checks.

Also introduce API rate limit in API gateway

Card column IDs in dynamodb

Using dynamodb table to save card column IDs

• Issue #8
• Issue #6
• Issue #7
• issue #9

PARENT CARD
Issue #3

Adding a new card

When adding a new card to the board, original column needs to be captured.

PARENT CARD
Issue #5

Adding tasks not found in dB into db

There could be a possibility that there are tasks that there are no entries in the dB.
One reason being, these tasks were created before this integration went live.

For those cards instead of throwing an error or ignoring those cases, at the time of card is being sent to closed, if said task is a recurring task, then add to the table.
Eventhough this is the card is being added to the table, it will not be sent back to the column where it came from.

After adding, make a comment and or add an emoji, so it stands out a bit.

Card reactions

When POSTing back a event body for a recurring task, associated reactions do not carried over.

Moving a card to CLOSED

PARENT CARD
Issue #7

Diagram and documentation

Make proper documentation

Creating a dynamobd table

To capture card info, create a dynamod card.

PARENT CARD
Issue #5

Deleting a card

when a card is deleted from the board, then DELETE that card entry from dynamodb table as well

PARENT CARD
Issue #5

Getting originating column ID

In the moved_column API, there is no depicting where the card was before i.e. it's previous column.
It only contains the new column id.

Since we need to send this recurring task back to the same column where it was, need to figure out how to get that value.

Setting Due Date

When setting due dates, date additions are done as whole integers.
Ex. For recurring task Monthly, it'll add 30 days to the the original due date.

This could be improved by doing introducing calendar date additions.

Updating a card

When updating a card, ie. when the card column is being changed, new column needs to be captured.
Note: if the new column in Closed then, these updates needs to handled carefully.

PARENT CARD
Issue #5

This is a test card

Get where from columnID for table

For recurring tasks, when moving back to from column, get that column from db