Set a record name on Kanban card creation

[Bonapara]

Current behavior

When creating a new record on a kanban board, you cannot set a name for the record from the kanban view. To name the record, you must go to the record detail page.

This doesn't apply to the opportunities kanbans where a specific behavior applies.

CleanShot.2024-09-09.at.17.23.03.mp4

Desired Behavior

We should implement the same behavior we have on table views: when creating a new record, we should display an input to set the record name from the board view. If the input is left empty, the card should be deleted, and the record should not be saved.

This doesn't apply to Opportunities kanbans.

The input label should be the object identifier. We should display the double input for people kanbans.

Table behavior to copy:

CleanShot.2024-09-09.at.17.37.35.mp4

[Faisal-imtiyaz123]

@Bonapara I would like to work.

[Bonapara]

Hi @Faisal-imtiyaz123, thanks! I believe it will be handled along with the other issue!

[Faisal-imtiyaz123]

@Bonapara Sure!

[ehconitin]

@Bonapara
I think Ill work on this.
I still cant figure out #7002 :(

[Faisal-imtiyaz123]

@ehconitin @Bonapara can i work on #7002 since @ehconitin hasn't been able to figure it out yet?

[ehconitin]

@Faisal-imtiyaz123
Please, go ahead.
Let me know if you need any help

[lucasbordeau]

Please @ehconitin could you drive this issue ? It's more important than #7002 and I'll be really busy with code review this week so I'll appreciate that you focus on this.

[ehconitin]

Got it!

[ehconitin]

@lucasbordeau
I am facing the same issue what I faced in #7002
I just cant think of an efficient way to render a card or dropdown in that particular stage or column when clicked on top right add '+', adding them from inside a column or stage is pretty straight forward.
Should we have something similiar to what we have for tables in RecordIndexPage, where we setPendingRecordId(v4()) and then setSelectedTableCellEditMode(-1, 0)
But then I couldnt figure how it would work in context of kanban.
Need help :)

[lucasbordeau]

Yes we should follow the same approach !

[lucasbordeau]

Each column has its own scope so you should find a way to get the scope of a column and then all the recoil component state can be called by passing this scope as a parameter.

We use the parameter precisely for this use case where we want to access the component states from outside of their context.

[ehconitin]

@lucasbordeau Got it! Will let you know if I get stuck somewhere!