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

Add Stage Management and "No Value" Column to Kanban #5987

Open
Bonapara opened this issue Jun 21, 2024 · 10 comments
Open

Add Stage Management and "No Value" Column to Kanban #5987

Bonapara opened this issue Jun 21, 2024 · 10 comments
Labels
good for experienced contributor scope: front Issues that are affecting the frontend side only size: hours

Comments

@Bonapara
Copy link
Member

Current Behavior

Records without a Select value assigned are not visible on the Kanban board displaying the given Select.

We cannot show/hide or reorder stages on a Kanban view.

Desired Behavior

We want to introduce a new Stage menu in the Kanban Options menu. This will allow users to choose which Select value should be displayed and in what order:

image

We also want to introduce a "No Value" column that should behave like other columns, with the possibility to show/hide it.

CleanShot 2024-06-21 at 18 39 11

Full Behavior

demo.mp4

https://www.figma.com/design/xt8O9mFeLl46C5InWwoMrN/Twenty?node-id=24955-194483&t=zLGqFerIr4FJfuka-11

@Bonapara Bonapara added scope: front Issues that are affecting the frontend side only size: hours good for experienced contributor labels Jun 21, 2024
Copy link

greptile-apps bot commented Jun 21, 2024

To add Stage Management and a 'No Value' column to the Kanban board, follow these steps:

  1. Add 'Stage' Menu in Kanban Options:

    • Modify KanbanOptionsMenu.js to include a new 'Stage' menu.
    • Update the state management in KanbanOptionsMenu.js to handle the visibility and order of stages.
  2. Introduce 'No Value' Column:

    • Update KanbanBoard.js to include logic for displaying a 'No Value' column.
    • Ensure the 'No Value' column can be shown/hidden by modifying the state in KanbanBoardState.js.
  3. Update Kanban Column Rendering:

    • Modify KanbanColumn.js to handle the new 'No Value' column similarly to other columns.
    • Ensure drag-and-drop functionality works for the 'No Value' column by updating KanbanDragDrop.js.
  4. Adjust Backend to Support New Column:

    • Update the backend API in kanbanController.js to fetch records without a Select value.
    • Ensure the backend supports the new stage management features by updating kanbanService.js.

Refer to the provided Figma design and video for UI/UX details.

References

@Sudarsh1010
Copy link
Contributor

I'd like to work on this.

@Bonapara
Copy link
Member Author

Hi @Sudarsh1010! Thanks! Maybe you can pick a good first issue first? This issue is for contributors with a bit more Twenty experience :)

@Sudarsh1010
Copy link
Contributor

yeah, My bad. I didn't saw the badge properly. Thank You.

@Us3r-gitHub
Copy link
Contributor

Do we plan to take action to change the 'select' field used in the view?
If yes, is this included in this issue??

@Bonapara
Copy link
Member Author

@Us3r-gitHub this is not handled by this issue indeed, for now, you would have to create a new view... Are you often in need of changing the view type?

@Us3r-gitHub
Copy link
Contributor

Are you often in need of changing the view type?

No, But I had dealt with issues #5915 related

When I develop, I create select fields and delete them over and over again
Sometimes, I just find a new bug (maybe)

When I delete a select field that is being used on a view, the view goes blank
That's right because select has been removed, but view must also be removed, right?
OR, we can add an action to change which select will be used

@Bonapara
Copy link
Member Author

Thanks for the detailed explanation, @Us3r-gitHub! I think the best solution is to delete the corresponding views simultaneously. We can also display a confirmation window in the settings when this field is deleted to inform the user that several views will be removed. Do you want to create an issue for this?

@Us3r-gitHub
Copy link
Contributor

It's possible to change 'select' after issue #6048 is resolved, right?

@Bonapara
Copy link
Member Author

@Us3r-gitHub yes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good for experienced contributor scope: front Issues that are affecting the frontend side only size: hours
Projects
Status: 🆕 New
Development

No branches or pull requests

3 participants