Skip to content
This repository has been archived by the owner on Jul 25, 2018. It is now read-only.

Access Restrictions / Limitations for Send to Clearing Handling #102

Closed
mcjaeger opened this issue Mar 3, 2016 · 4 comments
Closed

Access Restrictions / Limitations for Send to Clearing Handling #102

mcjaeger opened this issue Mar 3, 2016 · 4 comments

Comments

@mcjaeger
Copy link
Contributor

mcjaeger commented Mar 3, 2016

There should be restriction for sending to fossology in the way that not everyone can send anytime something to clearing. Every user should be able to send - for the items the users has created.

it should be attached to the edit release function - everyone who is permitted to edit a release can also issue a clearing.

But for further times, it does not make much sense (at least not for users) and if there is no (source) attachment, the option to send something to clearing should be deactivated.

@mcjaeger mcjaeger added this to the improvements milestone Mar 3, 2016
@mcjaeger mcjaeger modified the milestones: 1.5, improvements May 3, 2016
@mcjaeger
Copy link
Contributor Author

mcjaeger commented May 3, 2016

please note that user should only send to the clearing team where the user is allowed to. some kind of mapping of allowed clearing teams is required
Note that clearing team and sw360 group membership is not necessary 1:1. So mapping would be required.

@mcjaeger
Copy link
Contributor Author

(from discussion) actually one solution could be to show a dialogue to the user that the user is actually causing effort when sending "source attachment" to "clearing team".

@mcjaeger
Copy link
Contributor Author

should be after #128

@mcjaeger
Copy link
Contributor Author

This issue was moved to eclipse/sw360#7

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant