Issue Log (ID: TEM_ISL, Version 4.1.

4, Classification: Confidential)

Project Name Ultratech Marketplace Platform Project Code

Project Manager Vineela Mohanapu Last updated

Version # Status Version Date Author Reviewed By Approved By

0.5 Draft 10/14/2024 Vineela Mohanapu

Note for Status:

Draft – The work product or CI is in development and not sent or shared for review. In this state, changes or modifications can be mad
changing the versions.
Reviewed – The work product is Reviewed. In this state, changes or modifications can be made to the document as per Review Comm
changing the versions.
Approved – The work product is Approved by an authorized person/s. Any change from this state requires a new revision.
sification: Confidential)

ECUL24726

10/14/2024

Approval Date Description of the Modifications

nges or modifications can be made to the document without repeatedly

e document as per Review Comments from the Reviewer without repeatedly

quires a new revision.

Column Instructions For Completing This Document
Complete the Project Name, Project Manager Name, and Project Description fields
For each issue identified, complete the following:
A ID: A unique ID number used to identify the issue in the issue tracking log.
B Issue/Security Incident Description: This column should be populated with a description of the issue.
C Date Identified: This column should be populated with the date that the issue was identified.
D Entered By: This column should be populated by the name of the individual who first identified the issue.
E Is Escalation Required: Mention "Yes" if escalation is required and "No" if escalation is not required.
F Is RCA required?: This column should be populated with “Yes” if the program/project manager feels RCA needs to be performed to derive at the
cause of the issue.
G Root Cause: This column should be populated with the root cause of the issue.
H Impact: This column should be populated with a description of the impact of the issue. The impact may be expressed in terms of one or more of
the following: schedule, scope, resources, and space. The impact description should also include a reference to any milestones impacted.

I Issue Type: This column should be populated with the issue type. Valid options include the following: FRI, Procedural, System, Other. These are
defined as follows:

o Informational: The issue was generated and logged in response to a request for information external to the immediate project/project team.
o Procedural: The issue impacts process or procedure.
o System: The issue impacts systems (hardware or software).
o Other: The issue impacts other areas.

J Priority: This column should be populated with the Priority of the issue. Valid options include the following: High, Medium, Low. These are
defined as follows:

o Critical: Issue will stop project progress if not resolved.

o High: Issue will likely move the project back in terms of budget or timeline, or will materially affect quality or scope.
o Medium: Issue will have material effect on project, has potential to be moved to high category and/or requires significant resources to manage.
o Low: Issue is expected to have a moderate effect on the project, but will require resources to address.

K Current Status: This column should be populated with the issue's current status.

o Open: The problem is currently open but has not yet been addressed.
o Work In Progress: The problem is being actively worked to develop a resolution.
o Resolved: The problem has been fixed and closed in the system. All required actions to rectify the problem has been implemented.
o Closed: Problem has been reviewed and it is no longer considered as an active problem and can be closed without resolution. (Like
unreproducible bugs)
Some other potential options include:
o Late: The issue resolution is not yet resolved and it is past the expected resolution date.
o On Hold: The issue has been put on hold.
o Combined: Two issues found to be similar have been combined.

L Assigned To: This column should be populated by the name of the issue owner. ie.the individual most responsible for working towards resolving
the issue.
M Authorization for Critical/High: Mention the name of the person who authorised to take immediate action for critical and high issues

N Expected Resolution Date: This column should be populated with the date that the issue is expected to be resolved.
O Corrective action: This column should be populated with the Corrective/ Preventive actions identified as a result of performing RCA.

P Actual Resolution Date: This column should be populated with the date that the issue was actually resolved.
Q Verified by: This column should be populated with the name of the person who verifies the implementation of the CA and PAs, as applicable.

R Final Resolution & Rationale: This column should be populated with a description of the final resolution & rationale of the issue. The resolution
may be expressed in terms of one or more of the following: schedule, scope, resources, and space. The resolution description should also
include a reference to the milestones impacted.
Project Description:
Note: Alert notifications to the team members about all the issues through email shall be a part of issue management.
Categorization
Issue/Security Issue/Security
Date Is escalation
ID incident Entered By Is RCA required? Root Cause Impact Incident
Identified required?
Description Type
1 Theme Purchase 12th Aug, 24 Vineela Mohanapu No No Client is not finalized Project Schedule Other
the theme selection

UP Version: 11/30/06 Page 4 of 11

Project Description:
Note: Alert notifications to the team members about all the issues through email shall be a part of issue management.
Categorization
2 BRD Preparation 12th Aug, 24 Vineela Mohanapu No No Scope/Requirements Change in the Other
of few items are still features/functionaliti
pending from client es will consume
efforts to re-estimate
and planning

3 Thirdparty APIS 1st Oct, 24 Vineela Mohanapu No No Since the client is Project Schedule Other
planning to use the
existing services
app's seller/buyer
APIs, discussions are
ongoing to align on
the process and
integration approach.

UP Version: 11/30/06 Page 5 of 11

Project Description:
Note: Alert notifications to the team members about all the issues through email shall be a part of issue management.
Categorization
4 procuring 12th Aug, 24 Vineela Mohanapu No No The client is currently Project Schedule Other
matketplace evaluating multiple
extensions vendor extensions
and gathering
testimonials from
other clients to
inform their decision-
making process.

UP Version: 11/30/06 Page 6 of 11

Project Description:
Note: Alert notifications to the team members about all the issues through email shall be a part of issue management.
Categorization

UP Version: 11/30/06 Page 7 of 11

egorization
Expected Actual
Current Final Resolution
Priority Assigned To Resolution Corrective action Resolution Verified by
Status Rationale
Date Date
High Closed Vineela 23rd Aug, 24 Embitel team 08/27/24 Vineela The client has
Mohanapu suggested themes Mohanapu selected one of
to client and the extensions
provided demo from the list
aswell. shared by Embitel
and has assigned
a third-party
agency to provide
wireframes with
minimal changes
to the UI

UP Version: 11/30/06 Page 8 of 11

egorization
High Closed Vineela 23rd Aug, 24 few items are 09/12/24 Vineela We have captured
Mohanapu identified as CR,few Mohanapu all the client
items scope is requirements
considered as during the
magento default workshops and
flow. subsequently
connected with
the teams on calls.
Later, we
identified new
requirements that
are impacting the
timelines as
Change Requests
(CR) and shared
these with the
client. Due to time
constraints, we
will implement a
couple of features
using the default
out-of-the-box
(OOB) Magento
functionalities.

High Work In Progress Vineela 14rd Oct, 24

Mohanapu

UP Version: 11/30/06 Page 9 of 11

egorization
High Closed Vineela 30rd Aug, 24 Embitel has 09/24/24 Vineela We have
Mohanapu scheduled a call Mohanapu purchased the
with another client Land of Coders
to share their Marketplace
experiences with extensions
the vendor because the
extensions customizations
require less time,
and they support
most of the
features
requested by the
client.

UP Version: 11/30/06 Page 10 of 11

egorization

UP Version: 11/30/06 Page 11 of 11