You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Goals
- Enable authors to work based on tasks, for the tasks to be reviewed, and for the tasks to be promoted into a project, ready for release
Assumptions
- A task represents a work task
- A task is represented as a JIRA ticket within a specific project
- This task is also represented as a task branch on the terminology server
- A task can be linked to one or many SIRS (or equivalent) requests
Requirements
| # | Title | User Story | Importance | Notes |
|---|
| 1 | Creation of a task | As an author lead, I want to create a work task and assign to an author | | A JIRA ticket would be created on the specific project to represent the task |
| 2 | Creation of a task | As an author, I want to create my own task to deal with some content I have been asked to edit or create | | A JIRA ticket would be created on the specific project to represent the task |
| 3 | Adding content to a task | As an author, I want to work within a task and have the work I have done tracked for future reference | | All editing during the context of the task should be audited and retrievable against the task |
| 4 | Adding content to a task from a file | As an author, I want to import a list of concept IDs as a file to create the worklist within the task | | |
| 5 | | | | |
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Not Doing
- A JIRA ticket per concept