YTC is leveraging the Podio workspace for use in Issue Tracking accross multiple projects/workspaces.
These instructions will describe how to handle the issue tracking from both Infor and IMM along with descriptions of status and priority.
Podio was selected as a tool with the flexibility and visibility required to manage the IMM Issue List. The flexibility and
customization has allowed us to cater the collected information and workflows to keep everyone moving forward and issues being resolved
and tracked in an efficient manner.
Below are vidoes and information that will give you the necessary understanding of Podio and how we are leveraging Podio to manage the collection,
visibility and movement of issues from collected to closed.
Using and understanding how to use the filters within Podio really help you to drill into exactly what is important to you. Also learning
how some of the views in conjunction with filters can make the data more visibly relevant.
Using Custom Views
If there are a consistent number of filters you are always having to create to view the data you need it can be easier to create some custom views to more quickly drill directly into the data thats important to you.
Creating an Issue With Issue Introduction
So you have found an issue and need it logged. The Issue Introduction App within Podio will allow you introduct your issue for evaluation.
Once the issue is created using the Issue Introduction App it will be reviewed for possible duplicity and if found relevant be moved into the
master issue list and assigned a valid Infor Issue ID. Watch below for the steps necessary to create an issue for tracking using the Issue Introduction app within
the IMM Issue tracking workspace.
Issue Status Definitions.
Here is the list of possible status(s) that an issue can maintain, along with the definition and which team should be responsible for setting status.
*click on below status(s) to see further details.
This issue has been determined to require further evaluation. It may require that monitoring might be required
to determine the extent of the problem and/or if further information is required. This one is in stasis.
Issue has been resolved and deployed to IMM enviornment for re-testing. The associated IMM Engineer will be notified when this status is set and are responsible for
testing the issue to determine if original issue has passed re-test.
While researching the issue the Infor Engineer determined that this issue needs further information/logs from
IMM for continued resolutoin. This requires that the IMM Engineer associated re-evaluates the information attached and makes sure to add further
information to the issue to assist the Infor Engineer.
It is not required that Ingram Micro change the status of this issue when further information is added.
Here is how to determine what status to set your issue.
Low priority issues are usually cosmetic. They aren't critical to the functionality of the system but may indicate an incongruence with requirements.
These issues will be the last issues to be resolved
Medium priority indicates that this issue goes beyond just
cosmetic and could potentially have an impact on operations. These are desired fixes but not critical to the use of the system.
High priority indicates that this issue is required to be fixed before
go-live and could be potentially if not directly affecting the ability to complete testing objectives. Testing is being compromised by this issue however the system maintains stability.
Critical priority indicates that the system is compromised and testing is being halted by the inability to
manage past this defect. The system either crashes or is unable to move forward.