Issue Tracker
User Stories:
-
Prevent cross site scripting(XSS attack).
-
I can
POST
/issues/v1/{projectname}
with form data containing required
issueTitle,
issueText,
createdBy, and optional
assignedTo and
statusText.
-
The object saved (and returned) will include all of those fields (blank for optional no input) and also include
createdOn(date/time),
updatedOn(date/time),
open(boolean, true for open, false for closed), and
id.
-
I can
PUT
/issues/v1/{projectname}
with a
id and any fields in the object with a value to object said object. Returned will be 'successfully updated' or
'could not update '+id. This should always update
updated_on. If no fields are sent return 'no updated field sent'.
-
I can
DELETE
/issues/v1/{projectname}
with a
id to completely delete an issue. If no id is sent return 'id error', success: 'deleted '+id, failed: 'could
not delete '+id.
-
I can
GET
/issues/v1/{projectname}
for an array of all issues on that specific project with all the information for each issue as was returned when
posted.
-
All 7 functional tests are complete and passing.
Example Usage: