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 | JIRA Tickets |
|---|---|---|---|---|---|
| 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 | WRP-495 - Getting issue details... STATUS WRP-496 - Getting issue details... STATUS WRP-497 - Getting issue details... STATUS | |
| 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 | Importing a task to authoring service | As an author, I want to export my task to single concept/template-based authoring service so that I can work on my task. | |||
| 6 | Changing status of a task | As an author, I want to change status of task so that I can show the progress of my task. | |||
| 7 | Tracking request in a task | As an author, I want to track request, status of request, and requestor ID/name so that I can contact requestor when there is an issue of the request | |||
| 8 | Notifying user when a task is assigned to him/her by other user | As an author, I want to be notified when a task is assigned to me | |||
| 9 | Notifying user when any request in task has been modified | As an author, I want to be notified immediately when a request in my task has been modified so that I can have the latest information for authoring. | |||
| 10 | Merging a task into the specific project after it is completed | As an author, I want to merge my task into the specific project, which my task is belong to; so that another author can review my task. | |||
| 11 | Searching a task in many ways | As an author, I want to search task by
|
Workflow of task
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|
Not Doing
- A JIRA ticket per concept