| DMT Demand | JIRA Issue Type |
Workstream | Scope | JIRA Definition | Example | |
| Business Requirements ("what they want") |
Initiative | (none) | Year(s) | o A request expected to take more than 6 months o Requires a business case o Could group Epics by name (e.g. "PARIS 7: UDF", "PARIS 7: Reports") |
Version Upgrade | |
| Business Requirements ("what they want") |
Project | Epic | Month(s) | o A complex request expected to take 2-6 months o Links together several Stories o Generally described from Business or Manager perspective |
Clinical Care Plan | |
| Business Requirements ("what they want") |
Change Request | Story | Week(s) | o A request expected to take 1-6 weeks o May use Tasks to delegate work to other analysts/developers o May use Sub-Tasks to track steps needed for completion o Generally described from Business or Manager perspective |
Psychiatric Assesment V2 | |
| Business Requirements ("what they want") |
Quick Win | Story | Quick Win | Day(s) | o An expedited change request expected to take 1-2 days' work o Must not require a program-specific lead analyst or user engagement (e.g. workflow changes, training, user sign-off) o Must not require immediate prioritization |
Change Report Sort |
| Business Requirements ("what they want") |
Standard Order | Story | Standard Order | Hour(s) | o A regular, repeated request that takes a known number of hours o Requires a change-control (CC) email |
Picklist Update |
| Technical Requirements ("behind the scenes") |
**new** | Task | Week(s) | o A internal request expected to take 1-6 weeks o May be multi-program, or within a program or stream o Generally described from a Team or Team Lead perspective |
Review CC Process | |
| Technical Requirements ("behind the scenes") |
(Task Manager) | Task | Day(s) | o A delegated request that is expected to take more than a few hours o Linked to the delegating Story or Task |
Downtime Report | |
| Technical Requirements ("behind the scenes") |
(Task Manager) | Sub-Task | Hour(s) | o A delegated part of a Story or Task that can be assigned and tracked o Appears as a checklist box in the parent Story or Task |
Submit a CC Request | |
| Technical Requirements ("behind the scenes") |
Vendor Ticket | Bug | Vendor | ASAP | o Any issue that is logged to the vendor o Follows "Basic" workflow instead of "PCCIS" workflow |
Core functionality change |
| Technical Requirements ("behind the scenes") |
Incident | Bug | ASAP | o Any unplanned issue in production (non-vendor) o Follows "Basic" workflow instead of "PCCIS" workflow o Bugs marked as "Critical" will be highlighted as requiring immediate attention o Type can be changed to "Story" or "Task" if "PCCIS" workflow is desired or if need/priority changes |
A report fails to run |