Make all text on green cards visible on canvas
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 2
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 7
Description
**User story**
Several users map processes with a very long lists of suppliers, input, output and customers. Sometimes this is due to very complex process, sometimes just very bad and/or unclear process when these lists are long. In both cases seeing the entire list is valuable. **Information in Green cards (Supplier, Input, Output, Customer) needs to be visible on canvas without additional clickings**. If multiple Inputs and Outputs, it should also be possible to see which supplier supplies which input and which customers receive different outputs.
**User input 1 (by PK - SharePoint ID50)**
Mulighet for flere grønne bokser eller ekspanderende grønne bokser i SIPOCen. Kan være mange leverandører og kunder
**User input 2 (by TK - SharePoint ID70)**
Green cards (Supplier, Input, Output, Customer) should grow vertically when the content is more than what is visible.
**User input 3 (by MU - SharePoint ID85)**
I would like to use this tool for an ongoing improvement project. Because we in this case have several suppliers, inputs, outputs and customers (green labels), we have to use Whiteboard instead. I hope this soon will be a possibility :-)
As of now, only the top of these lists are visible on the canvas.
Suggested solutions
a. automatically expanding green cards vertically to show all text
b. make it possible to add more green cards vertically
Contributor guide
Research direction
Start at the canvas rendering for green Supplier, Input, Output, and Customer cards. Reproduce the issue with long lists, then compare automatic vertical expansion with adding multiple cards and determine how supplier-input and output-customer relationships should remain visible. Done means the full text is visible without extra clicks and the relevant relationships remain understandable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100