User story (meta) #2268

Improve the ergonomy of the Administration > Archives screen

Added by Jonathan CLARKE over 2 years ago. Updated almost 2 years ago.

Status:Discussion Start date:2012-02-10
Priority:2 Due date:
Assignee:- % Done:

0%

Category:Webapp - Administration
Target version:Ideas (not version specific)
Needs translating:No

Description

A lot of separate user stories have added features to this new screen (#2074, #2098, #2099, #2101, #2102).

I feel that it's ergonomy could be improved: we have lots of "widgets" that do almost the same thing, but not quite, which is quite confusing. I'm not sure how to do this best yet, so I'm opening this issue to not forget and to enable us to discuss this.

I wonder if we could have just two widgets: Export and Import.
The export widget could have a list of checkboxes: [ ] All [ ] Groups [ ] Policy instances and user template library [ ] Configuration Rules, and a button to export which would run the different exports according to what was selected.
The import widget could have a list of radio buttons: ( ) All ( ) Just groups ( ) Just policy instances and user template library ( ) Just configuration rules, and when one is selected, an AJAX function could update the list of available archives to import.

Thoughts?

History

#1 Updated by François ARMAND over 2 years ago

That may be a good idea. Nonetheless, I don't see how in that scenario the different version of archive can be managed.

So at least, that would have to be radiobox.
Perhaps I can try to build the screen for the next alpha, and so we could have the two options to see what is the best to use, and we will remove the worst of the two.

#2 Updated by Jonathan CLARKE over 2 years ago

François ARMAND wrote:

That may be a good idea. Nonetheless, I don't see how in that scenario the different version of archive can be managed.

So at least, that would have to be radiobox.

Yes, for imports. That's what I said above: "The import widget could have a list of radio buttons [...] and when one is selected, an AJAX function could update the list of available archives to import". Or did I miss some other requirement?

Perhaps I can try to build the screen for the next alpha, and so we could have the two options to see what is the best to use, and we will remove the worst of the two.

Sounds good!

#3 Updated by François ARMAND over 2 years ago

Ah, no, I just misread the text.

One more validation, thought: does checking both groups, policy and configuration rules for import should also check All ?

#4 Updated by Jonathan CLARKE over 2 years ago

François ARMAND wrote:

Ah, no, I just misread the text.

One more validation, thought: does checking both groups, policy and configuration rules for import should also check All ?

Yes, that seems to make sense.

#5 Updated by Jonathan CLARKE over 2 years ago

  • Target version changed from 2.4.0~alpha6 to 2.4.0~alpha7

#6 Updated by Nicolas PERRON over 2 years ago

Why this ticket has no assignee ?

#7 Updated by Jonathan CLARKE about 2 years ago

  • Target version changed from 2.4.0~alpha7 to 2.4.0~beta1

#8 Updated by Jonathan CLARKE about 2 years ago

  • Target version changed from 2.4.0~beta1 to Ideas (2.4 specific)

#9 Updated by Jonathan CLARKE almost 2 years ago

  • Target version changed from Ideas (2.4 specific) to Ideas (not version specific)

Also available in: Atom PDF