Keep track of User IDs in a service
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
Pre-checklist
-
I have searched for, and did not find, an existing issue at the top-level.
Stories
Story 1: As a developer I want a user service so that I can access the list of users from any component necessary.
Ready checklist
-
Independent (of other issues in flow) -
Negotiable (and negotiated) -
Valuable (the value to an identified role has been identified) -
Estimable (the size of this story has been estimated using /weight value
or the menu on the right) -
Small (can be completed in 50% or less of a single iteration) -
Testable (has testable acceptance criteria)
Also
-
Appropriate role labels have been applied (e.g., role:*
). -
Relevant activity labels have been applied (e.g., activity:*
). -
Linked to related issues, epics, and milestones.
Diagrams
Acceptance Criteria
Scenario: I create a new component that needs to list users
Given the user service
When I import the service
Then I can access the list of users
Testing
Code coverage should be at least 80%
Template Version 2.0.0
/label type::user
Edited by James Young