| Target release | |
|---|---|
| Epic | |
| Document status | DRAFT |
| Product | |
| Design | |
| Development | |
| EIA | |
| QA | |
| PMO | |
| Reviewers |
Goals
- Document standard Design/Document approval workflow for Mike G
Tasks
- Document standard design and/or document approval workflow and share
- Document user requirements and feedback (design team)
- Adam Grandy to review
- Review with Mike G + Peter G (Engineering)
- Create Omnigraffle diagram of various desired workflows
Background and strategic fit
Following discussion with Mike, Peter, and Nareg Burr, Adam Grandy and Angela Glass were asked to document the Product + Design workflow. Peter asked to see the entire workflow in one view (see development workflow), and Mike would like to see the standard JIRA document approval workflow (also employed or customized for design studio approvals). This page is to serve for that request.
Assumptions
- Reviewers have understanding of workflow 3 simple steps for bringing your design review process into Jira Software:
design review workflows in Jira Software
Now that you have a clear picture of the process, it’s time to bring it into your Jira Software projects. To improve creative project efficiency from job request through to approval, you can use workflows to help you track and manage creative requests and review progress.
The following workflows, custom tasks, and sub-tasks will help to help you track, manage, and speed up creative work from request right through to approval. They are most effective when used together as part of a workflow scheme, though there may be some projects where you only need to use one or the other, depending on your process.
A workflow scheme defines a set of associations – or mappings – between a workflow and an issue type. Workflow schemes are associated with a project and make it possible to use a different workflow for every combination of project and issue type.
Your first workflow will track creative work from start to finish, so you can see what work needs to be assigned, what’s in progress, and what’s waiting for approval. Like this...
- Reviewers are aware of standard JIRA Business Templates, e.g. Document approval:
Document approval
Work item: Document
Custom Fields: Client, Reference
Use case: Some documents have legal and financial impact on the company. Documents like legal contracts and policies require traceability and accountability of changes and updates. The Document approval template allows teams to gather the right information and create an audit trail so that teams can see who, what, and when edits were made.
Requirements
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | ||||
| 2 |
User Research
Atlassian product design and development process.
User interaction and design
Analytics
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|
Not Doing
Usability
