[ 
https://issues.apache.org/jira/browse/AIRAVATA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648103#comment-15648103
 ] 

Marcus Christie edited comment on AIRAVATA-2195 at 11/8/16 4:58 PM:
--------------------------------------------------------------------

UI wise I'm thinking of something like this:

!project_owner.png!

There will be a box showing the project owner that cannot be dismissed or 
changed, thus showing that the project owner has implicit read/write permission.

This project owner box would only be shown if the project owner is not the same 
as the current user.  So, in the example above, when User C clones the 
experiment in User A's project and changes the sharing, User C will see that 
User A is the "project owner" for that experiment.


was (Author: marcuschristie):
UI wise I'm thinking of something like this:

!project_owner.png|thumbnail!

There will be a box showing the project owner that cannot be dismissed or 
changed, thus showing that the project owner has implicit read/write permission.

This project owner box would only be shown if the project owner is not the same 
as the current user.  So, in the example above, when User C clones the 
experiment in User A's project and changes the sharing, User C will see that 
User A is the "project owner" for that experiment.

> Shared user will end up with an experiment which he has no permission to view
> -----------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2195
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2195
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway
>         Environment: https://dev.seagrid.org
>            Reporter: Eroma
>            Assignee: Marcus Christie
>             Fix For: 0.17-SNAPSHOT
>
>         Attachments: Screen Shot 2016-10-25 at 3.04.35 PM.png, 
> project_owner.png
>
>
> Steps;
> 1. User A creates a a project and shares it with user B and user C
> 2. user A creates an experiment which is shared with both users B and C
> 3. User C clones and creates a new experiment and removes User A from the 
> experiment. Only the experiment is shared with usr C
> 4. User A removes the sharing from both users at project level.
> 5. Both users cannot view the project now.
> 6. Both users can see the cloned experiment in Experiment Browse but cannot 
> view the experiment details. Throws exception attached
> First if using owners project to create experiments should not be able to 
> remove the owner from the experiment or the project
> Secondly if permission is denied should handle with correct error messages. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to