[jira] [Updated] (SOLR-17924) Create Configset Dialog

["Christos Malliaridis (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-17924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christos Malliaridis updated SOLR-17924:
----------------------------------------
    Fix Version/s: 10.1
                       (was: main(11.0))

> Create Configset Dialog
> -----------------------
>
>                 Key: SOLR-17924
>                 URL: https://issues.apache.org/jira/browse/SOLR-17924
>             Project: Solr
>          Issue Type: Sub-task
>          Components: Admin UI
>            Reporter: Christos Malliaridis
>            Assignee: Christos Malliaridis
>            Priority: Major
>              Labels: new-ui, newdev, pull-request-available, ui
>             Fix For: 10.1
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> In the configsets section of the new UI the user should be able to add a new configset.
> h2. Task
> Implement the configset dialog that allows the user to create a new configset and that uses existing configsets.
> h2. Acceptance Criteria
> - The user can insert a name for the new configset
> - The user can choose a base configset from the existing configsets
> - The dialog's dropdown for selecting a configset may use the currently selected configset from the Configsets section as default
> - The default configset (_default) is selected by default
> - When the configset is successfully created and the dialog is closed, the ConfigsetsComponent from the section updates its current selection options and selects to the new congiset
> - The dialog is closed if the configset is created successfully
> - The dialog shows the error if a configset could not be created for some reason
> - The configset name is validated with the existing configsets
>     - existing name conflicts are shown as error in the input field
>     - no request is sent in case of a conflict
> You should not implement hte configset import feature that is currently present in the designs, as this will be a separate task.
> h2. Additional Information
> The existing ConfigsetsComponent interface may be reused and the DefaultConfigsetsImplementation may be updated if used and changes are necessary. Avoid code duplication if the same functionality is in the existing components (e.g. configset selection dropdown). 
> For the edge-case where no configsets are available (not even _default) a request should be sent without a baseConfigset set. If the missing default configset triggers an error it should be shown to the user. No further error handling has to be implemented.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org