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

Christos Malliaridis updated SOLR-17846:
----------------------------------------
    Description: 
One of the key resources of Solr are configsets. User should be capable of 
managing configsets freely with all their features.

h2. Scope

The scope of this ticket is the entire configset section. Devs should work on 
sub-tasks so that PRs are kept small enough and reviewable.

h2. Acceptance Criteria

This ticket can be closed once all sections of the "Configsets" are defined, 
designed and implemented.


  was:
One of the key resources of Solr are configsets. User should be capable of 
managing configsets freely with all their features.

h2. Scope

The scope of this ticket is the entire configset section. Devs should work on 
sub-tasks so that PRs are kept small enough and reviewable.

h2. Acceptance Criteria

This ticket can be closed once all sections of the "Configsets" are defined, 
designed and merged.



> Introduce Configset Management in Admin UI
> ------------------------------------------
>
>                 Key: SOLR-17846
>                 URL: https://issues.apache.org/jira/browse/SOLR-17846
>             Project: Solr
>          Issue Type: New Feature
>          Components: Admin UI
>            Reporter: Christos Malliaridis
>            Priority: Major
>              Labels: new-ui, ui
>
> One of the key resources of Solr are configsets. User should be capable of 
> managing configsets freely with all their features.
> h2. Scope
> The scope of this ticket is the entire configset section. Devs should work on 
> sub-tasks so that PRs are kept small enough and reviewable.
> h2. Acceptance Criteria
> This ticket can be closed once all sections of the "Configsets" are defined, 
> designed and implemented.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to