maibornwolff / retro Goto Github PK

Currently the maximum amount of characters allowed for the card content is 10000. Some people requested to increase the size, since they write sometimes more text than usual.

Users can define in their settings a timebox for each item that will be discussed.

The use case would be something like this:

Sometimes when we discuss about an item and there could be some relevant information about it (e.g. a link), then people started to share this information via the chat of the video client. With this feature all relevant information or just some comment could be attached on that retro item itself.

Introduce useful keybindings to enable a smooth workflow. E.g. for item creation, deletion etc.

We definitely need to add tests before release and setup a CI server

Since TravisCI did some shady moves lately, I'd personally feel more comfortable by using CircleCI.

https://github.com/diegohaz/constate

reduces boilerplate

In the Homepage you will have an option to start a planning poker session. After clicking it you start a new sprint planning context at /planning/:id.

The planning procedure will be very basic.

All users see a list of cards they can choose for each story to vote. When the moderator starts the poll. Everyone has one vote. The moderator can start a re-vote.

All dialogs display an error state by default, when e.g. a textfield is empty at first. From a UX perspective is this not a good practice. We should highlight nothing at first and after an interaction with the form field, we highlight the error message in the error case.

There are use cases, where people don't want their board to be deleted. In order to prevent deletion from the cronjob, we need to add some sort of toggle. which tells us to not delete this board.

Like you see it in every chat app. As long as someone is writing something or has a "create card" modal open, we display something like Participants are writing ...

The moderator can specify the amount of votes each user has.

• If the privacy mode is on, then all cards are blurry at creation
• If the privacy mode is off, then all cards are not blurry

Add reactions like known in Facebook for cards

The project currently works with the filesystem. To ensure performance and relief the server from too many filesystem accesses, we need to introduce a database. That means that we have to change the whole backend API from the fs module of Node.js to an appropriate DB API

A feature request, where the moderator has the ability blur and unblur columns separately

Reproduction:

• create a column with two items in it
• like one item and then try to like to other one ==> width of the other one shrinks

These are the files, using styled components

Board.js

• Container -> rename to BoardContainer

Column.js

• Container -> rename to ColumnContainer
• StyledTitle (has component as argument) -> rename to ColumnTitle
• ItemsContainer
• ColumnHeader
• ButtonContainer
• ColumnActionButton (has component as argument)

Header.js

• Container -> rename to HeaderContainer
• StyledTitle (has component as argument) -> rename to BoardTitle

Item.js

• Container -> rename to ItemContainer

Users have the ability to cluster items on the board, that may have similar content

There are some common retrospective formats. Instead of creating these formats manually, the user can automatically generate it automatically

Users have the ability to export their board as PDF when their retrospective is finished

You can trigger timeboxing by a mechanism (e.g. button) in order to start a timer, which runs as long as the user defined.

In retrospectives, you actually do the clustering before voting. So this might be not a real issue. To get 100% sure about it, it wouldn't hurt to investigate a bit about this.

If I get a link to a board and join it, I want to see the current board

We definitely need more tests, since some are missing and we also have new features again, that are untested.

We need some manual testing in order to see what works and what's not

When you drag a column, it expands into the full page height instead of its original height. Violates POLA in my opinion.

Vote count can be set to negative numbers .
Should go max. down to 0 Votes.

(Or is there a use case I am not aware of, that requires negative votes?
Downvoting could be restricted, aka "Max. 3 downvotes", but that seems to me like a new feature and mostly not needed in typical retrospective circumstances)

Add some functionality for the moderator to raise attention

https://reactjs.org/docs/hooks-reference.html#usecallback

https://blog.hackages.io/react-hooks-usecallback-and-usememo-8d5bb2b67231

Columns can have different colors in order to distinguish problem- and solution space. Furthormore provide a special card that resembles an Action Item

If we reach the time limit of a discussion, we pop up a dialog where every user can either vote for or against a continued discussion.

react-beautiful-dnd provided since v12 a virtual list support. This feature might be really handy

https://reactjs.org/docs/context.html

The moderator can activate the private mode in order to blur items in the writing phase

Some teams apparently have the following workflow:

• Everyone creates their cards
• Then each user introduces all its cards

A filter would make this process easier, since you don't need search for it the hard the way

Currently, we are blurring all cards. We need a way to just blur the cards that are not owned by the participant

A feature request, where the moderator can export the board metadata and can create a new board based on this metadata. The provided use-case was that e.g. person A is creating a board template and provides this template for person B. So both work with the same initial state, but can modify it how they want in their teams.