| Page properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- 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 | Sprint | 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. | 4 | 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. | 1 | A JIRA ticket would be created on the specific project to represent the task |
| |||||||||||||||||||||||||||||||
| 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 reference2 | 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 task3 |
| |||||||||||||||||||||||||||||||||
| 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. | 2 |
| ||||||||||||||||||||||||||||||||
| 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 | 3 |
| ||||||||||||||||||||||||||||||||
| 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. | 6 | |||||||||||||||||||||||||||||||||
| 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
| 2 |
|
Workflow of task
...
Authoring task workflow
...
Workflow in P
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
...
In progress: when an author starts working on a new task, it will enter this state. When classification is failed because of classification errors, it will come back to this state from 'Classification'. When classification is completed with no errors but author modifies any concepts have been classification, it will come back to this state from 'Classification' and author has to classify the task again. When reviewing is completed by an reviewer but it has errors in the task, it will come back to this state from 'Peer review'.
Classification: when an author clicks the 'Classify' button, it will enter this state.
It includes editing, classification, validation, and rebasing (to discover conflicts between tasks in the same project).
In Peer 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.
Escalation: when editing author and reviewing author have different opinions in a task, it will enter this state. Authoring team will discuss the issues in this task and provide a final decision.
Ready for promotion: when Review completed: after a task is reviewed by reviewer and there is no need to make any changes in this task the task status has been manually changed from "Review in progress" to "Review complete in Review view, it will enter this state.
Promoted to project: 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 has with no conflict conflicts and author is ready merged to close the taskmainline, it will enter this state.Pending answer: when an author has to clarify a request or put a request on hold, it will enter this state. After a certain time (need to be defined by authoring team), if author cannot get response from requestor, then author will remove that request from the task. The status of the task will be changed to 'In progress' then.
Questions
Below is a list of questions to be addressed as a result of this requirements document:
...