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 - done and implemented
| # | Title | Requirement Description | User Story | Notes | JIRA Tickets | |
|---|---|---|---|---|---|---|
| 1 | Creation of a task | It must allow to
| As an author lead, I want to create a work task and assign to an author so that author can receive a task from author lead directly. | A JIRA ticket would be created on the specific project to represent the task
|
| |
| 2 | Creation of a task | It must enable to
| As an author, I want to create my own task to deal with some content I have been asked to edit or create so that I can provide summary of my task. | A JIRA ticket would be created on the specific project to represent the task | WRP-495 - Getting issue details... STATUS WRP-496 - Getting issue details... STATUS WRP-497 - Getting issue details... STATUS | |
| 3 | Adding content to a task | It should require author to provide free text. For example
Note: this requirement is only for minimum viable product but not the final delivery. | 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 | It should allow author to upload a list of request IDs as a file into task. Note: this requirement is only for minimum viable product in phase 1. | As an author, I want to import a list of request IDs as a file to create the worklist within the task |
| ||
| 5 | Changing status of a task | It must be able to
| As an author, I want to change status of task so that I can move forward my task to the next state. | |||
| 6 | Notifying user when a task is assigned to him/her by other user | It must
| As an author, I want to be notified when a task is assigned to me |
| ||
| 7 | Notifying user when any request in task has been modified | It must notify user when any requests in task has been modified in request management tool | 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. | |||
| 8 | Searching a task on dashboard | It must be able to search a task on dashboard by any column or text search | As an author, I want to search task by
|
|
Workflow of task
Authoring task workflow
New: when a task is created by author, it will be in this state.
In progress: when an author starts working on a new task, it will enter this state. It includes editing, classification, validation, and rebasing (to discover conflicts between tasks in the same project).
In review: when an author clicks the 'Ready for review' button, it will enter this state. The authors with reviewing role will see this task in the 'Review Tasks' list on the dashboard.
Review completed: after a task is reviewed by reviewer and the task status has been manually changed from "Review in progress" to "Review complete in Review view, it will enter this state.
Promoted: when a task is rebased with no conflicts and promoted to the project level in TS, it will enter this state.
Completed: when the task promoted to the project level with no conflicts and merged to the mainline, it will enter this state.
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