...
Once edits are submitted, the workflow is as follows:
- Confluence Editor edits page and publish page(s)
- Confluence Editor submits page for publishing approval
- Automated Page Approval request emailed to Approver
- A JIRA Service Desk ticket is created by an Approver, signaling confirmation of publishing request
- Page is Approved or Rejected and the JIRA ticket updated
- T&D PO notifies Confluence Editor of page status through the Jira ticket
- This process continues till the page is approved and published
...
| Note |
|---|
NOTE: Each submission results in a ticket. Users should wait until all edits are completed before submitting for approval (insert link to end-user documentation). |
Section Edit/Service Request Workflow
A Confluence Editor would use the Service Request Workflow when the edits are equal to overhauled or new pages (2 or more)
The workflow is as follows:
...
...
Publishing Timeline
| Lucidchart | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- Submit - as soon as edits have been made and saved; allows the Confluence Editor to submit for approval or return to continue editing
- In Review - page has been submitted to Approvers; no further edits should be made to the page
- Resubmit - appears if the page has been sent back to the Confluence Editor for further edits
- Reapprove - page has been resubmitted to Approvers; no further edits should be made to the page
- Published - indicates the page has been approved and that end users can see the most updated information
...
- approved
Special Cases and High Priority Content Publishing
In case of immediate need, the PO will have to work with the client and the T&D team to develop a viable plan to see to these needs. The factors that require immediate service is are defined and determined by the PO in conjunction with the T&D Team Lead.
...