Wrike Statuses

Overview

With the recent introduction of Wrike across the various Vision departments, the Products team decided to also leverage the new tool. Overall, the goal is to provide greater transparency, refresh the current process, and support product marketing requests related to smaller enhancements.

After a request is submitted or a bug is reported, each respective ticket will follow a custom workflow. These workflows consist of different statuses when comparing the "Bug Board" to the "Request Wall" and you can see detailed descriptions of the tables below.

What does each "Bug Board" status represent?

Stage	Status	Meaning
Active	New	Default status for all incoming issues
Active	Information Needed	If Products needs additional information or context, a follow up conversation will be requested
Active	Logged in TFS	Formally reviewed; Products is aware of the issue
Active	Scheduled	Will implement; a date range or more formal schedule is determinable
Active	In Development	Scheduled for a sprint; pending final solution
Active	Ready to Ship	Bug fixed in 1 of 4 possible sprints; pending release
Completed	Shipped	Issued fix to all relevant clients
Deferred	Planned	Reported bug will be addressed when time is available; non-critical issues
Cancelled	As Designed	Reported bug behaves as designed; submit a "Request Feature" form for additional action
Cancelled	Cannot Reproduce	Development team or QA cannot replicate; more information may be needed

What does each "Request Wall" status represent?

Stage	Status	Meaning
Active	Under Consideration	Products will consider all requests submitted; requests stay marked with this status until formally reviewed
Active	Information Needed	If Products needs additional information or context, a follow up conversation will be requested
Active	Scheduled	Will implement; a date range or more formal schedule is determinable
Active	In Development	Requests which are actively under development will retain this status
Active	Ready to Ship	Features marked as resolved by a developer, but still need to pass 'Release QA'
Completed	Shipped	Items are now included in a Vision product (e.g., visionLive); able to actively discuss with all clients additional details
Deferred	Planned	Likely to be developed at a future date, but cannot guarantee / commit to a specific date range based on higher priorities today
Deferred	Future Consideration	Long-term consideration for development, but will require additional support.
Cancelled	Already Exists	This feature request or product idea already exists in one of Vision's products.
Cancelled	Will Not Implement	Unlikely to implement these features; may require a customization due to niche request