Feature picker || Custom feature is shown as form even after adding the feature

[vikasrohit]

As per design the custom feature should be shown in the same way we are showing standard features i.e. without any form. However, right now we are showing the custom feature in a form. Once added, user does not have any option to save that feature so does not makes sense to show the feature in the form.

[vikasrohit]

cc: @fnisen @vic-appirio @parthshah

[vikasrohit]

Tracking with asana task https://app.asana.com/0/95614844085038/184327383400574

[parthshah]

My 2 cents.. custom features should be shown as a form always. The form should be disabled (for updates) if the user does not have edit access to the project.

[vikasrohit]

Makes sense, but once the feature is added, there is no save/update button (only delete button is there) for the user when user has the edit access. So, to enable the user update the custom feature we need to show save/update button along with the delete button.

[parthshah]

Just like regular features we should have auto-save / update for custom features. NOTE: for now auto-save will save it back to specification page user would still have to click save to persist it to DB.

[vikasrohit]

Okay, should we then remove the save button altogether. I mean to be consistent, should we remove the save button which we show initially?

[fnisen]

I don't completely understand the question, so my two cents may not be helpful, but there is actually a two part experience:

• Creating the feature, which has the save button (and no pill selector) and adds the feature to your list and turns it "on":

• Turning the feature on and off with the pill selector and (separately) deleting it from your list of potential features:

[vic-georgiev]

It seems like the problem is the description field not being able to be edited once the feature is created. What we can do is to follow the regular pattern and always show the text area - being editable. This is to say that a custom feature would behave like a regular feature with the addition of a "Delete" button underneath. @fnisen would that be a solution? Good point, @vikasrohit @parthshah