search

jbenn313 / itsy-bitsy-spider

0 stars 0 forks source link

Add Huge partner group #1

Open jbenn313 opened 7 years ago

jbenn313 commented 7 years ago

Priority (High, Medium, Low)

High

Description (Brief)

Add the Huge partner group

Acceptance criteria (Exhaustive)

  1. The standard test user is created and added to group. For Huge this would be user huge-teste-1 in the group named "huge-group".

  2. huge-teste-1 is able to view the Huge parceiros folder at /content/dam/parceiro/huge.

  3. huge-teste-1 can create, delete, and modify assets at /content/dam/parceiro/huge.

  4. huge-teste-1 user is not able to view any of the other partner project folders at /content/dam/parceiros. For example, content/dam/parceiro/sunset is invisible huge-teste-1.

  5. /content/dam/parceiro/huge is invisible to sunset-teste-1.

  6. /content/dam/parceiro/huge is invisible to dm9-teste-1.

  7. When a Huge project is created, it is possible to assign huge-teste-1 to the project.

  8. huge-teste-1 is able to view the Huge projects folder at /content/dam/projects/huge.

  9. huge-teste-1 can create, delete, and modify assets that are within a projects assigned to huge, for example at /content/dam/projects/huge/.

  10. huge-teste-1 user is not able to view any of the other partner project folders at /content/dam/projects. For example, content/dam/projects/sunset is invisible huge-teste-1.

  11. /content/dam/projects/huge is invisible to sunset-teste-1.

  12. /content/dam/projects/huge is invisible to dm9-teste-1.

  13. huge-teste-1 is able to assign a review task to any AEM user

  14. huge-teste-1 is able to create a Project Approval workflow.

  15. huge-teste-1 is able to share a link via link sharing.

Technical considerations (Optional)

  1. For implementation purposes, the huge-group partner group can be modeled after sunset-group or dm9-group. Both of these exhibit the behavior described above.
jbenn313 commented 7 years ago

Test results on Monday June 26, 8 AM

  1. I took care of this one. Please let’s always do this in Stage, for testing.
  2. OK
  3. OK
  4. Fail. Concrete is visible.
  5. Fail. Sunset can see Huge.
  6. Fail. DM9 can see Huge.
  7. OK
  8. OK
  9. OK
  10. Fail. All other partner folders are visible.
  11. Fail. Sunset can see Huge projects.
  12. OK
  13. OK
  14. OK
pguasti commented 7 years ago

Test results on Friday June 30, 4 PM

I've been running a few tests in stage to solve these pointments:

  1. I've adjusted the view permission at Huge Group and now "concrete" is not checked. Apparently now it works.
  2. Fixed! Sunset group was able see "Huge" and "concrete" group and now I've blinded them.
  3. Fixed! DM9 group now can only see DM9 projects.
  4. Here I have a question, huge-teste-1 user is under huge's group and its permissions. Why do we still have to uncheck a single user permissions to unable him to see the other partners projects?
  5. Strange, because sunset group and sunset-teste-1 are restricted to see only sunset project folder. Where do we fix it?

One last thing, when a new partner gain access, we create: 1- single user, 2- group, 3- project folder in "projects" 4- new folder at the repository.

We tried to input a new partner, and we created a project folder at /content/projects, but it hasn't appeared at the user permission structure in aplication and system configurations, do you know why?