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.

Sign up for GitHub

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

Jump to bottom

Modelling 'involved user' in ServiceRequest #482

Open
cstockloew opened this issue Jun 3, 2017 · 1 comment
Open

Modelling 'involved user' in ServiceRequest #482

cstockloew opened this issue Jun 3, 2017 · 1 comment
Labels
discussion feature request

Comments

@cstockloew
Copy link
Member

cstockloew commented Jun 3, 2017 •
edited by amedranogil

Currently Involved user is not very semantic, as there is always the question is the involved user the one behind the issueing of the service request or the one affected by the service request.
Having these distinct roles helps with security.
Old interface can be mapped to be issuer and affected the same as involved user.
@amedranogil
Copy link
Member

update

@amedranogil amedranogil reopened this Jun 9, 2017
@cstockloew cstockloew changed the title GForge placeholder - trackeritem 482 Modelling 'involved user' in ServiceRequest Jun 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@amedranogil @cstockloew