Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Library categories management issues #221

Closed
ruslanbaidan opened this issue Dec 19, 2019 · 3 comments
Closed

Library categories management issues #221

ruslanbaidan opened this issue Dec 19, 2019 · 3 comments
Assignees
Labels
bug

Comments

@ruslanbaidan
Copy link
Contributor

@ruslanbaidan ruslanbaidan commented Dec 19, 2019

The issues description

The issues are applicable for BackOffice and FrontOffice parts.

  1. Root categories ordering issue.
    When we create a root category there is a property to specify the position of the element (in the beginning, in the end or after an element), but new Categories are always created in the beginning. When we edit the category position, it doesn't have any impact, category position stayed the same.

  2. Disappeared library sub categories including their assets.
    When we create 2 root categories and one of them already has (or we create) child categories with different assets, and then try to set the other root category as child of the first root one in the beginning of the list, the subcategories of the root one are disappeared.
    Sometimes the scenarios could be different and not all the categories are not displayed, but 1 or 2 only.

To Reproduce

Steps to reproduce the issue #1:

  1. Create a new analyse based on Cases Model, if you don't have a test one.
  2. Chose an asset from the lib, create and set a new root category for it, category position can be in the end or after another category, save the asset.
  3. Do the same for another element.
  4. The categories will be in the top and the second created will be the first one.
  5. Try to modify one of the root categories position. It doesn't affect its position.

Steps to reproduce the issue #2:

  1. Create a new analyse based on Cases Model, if you don't have a test one.
  2. Choose an asset from the lib, open the edit UI and create a new root category, save the asset.
  3. Do the same for another element.
  4. Choose another asset and create a new sub category for it, which is child of the first root one, save the asset.
  5. Do the same for another element. As the result, the first root category should have a 2 or more sub directories.
  6. Edit the asset which is under the second root category, edit its category and set the parent one the first root. (position suppose to be in the end).
  7. After saving the asset all the other categories under the first root one are disappeared.

Expected behaviour

The issue #1: Category should be placed on the specified position.

The issue #2: Display all the categories after the described operations.

Additional context
Different library categories management issues were fixed within the following task:
#216
There are some related parts of the code still require modifications.

@ruslanbaidan

This comment has been minimized.

Copy link
Contributor Author

@ruslanbaidan ruslanbaidan commented Dec 19, 2019

Screenshot 2019-12-19 at 17 06 07
Screenshot 2019-12-19 at 17 07 30
Screenshot 2019-12-19 at 17 07 59
Screenshot 2019-12-19 at 17 16 17
Screenshot 2019-12-19 at 17 16 37

@ruslanbaidan

This comment has been minimized.

Copy link
Contributor Author

@ruslanbaidan ruslanbaidan commented Jan 9, 2020

MONARC Development Overview automation moved this from To do to Done Jan 10, 2020
@ruslanbaidan

This comment has been minimized.

Copy link
Contributor Author

@ruslanbaidan ruslanbaidan commented Jan 10, 2020

Released to production ver. 2.9.8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
MONARC Development Overview
  
Done (deployed on prod)
1 participant
You can’t perform that action at this time.