Defect Creation Guide

The defects are opened in JIRA as follows:

**These are screenshots of the JIRA defect creation list, taken in pieces to
explain each area **

Issue Type: Defect (ALWAYS DEFECT) (when you begin to create a defect, it
will default on epic sometimes, so please make sure to change it to defect)
Assignee: this will auto populate after creating the defect. It will either
assign to a specific person or it will say Unassigned, that is fine
Summary: Needs to include project, build #, where the defect is happening
and brief description.
[BRAND ENVIRONMENT BUILD #] Area of Defect Description
***That is how the defect should look, examples are below since there are
various ways to log a defect, if it is in multiple environments, multiple
brands, adaptive, etc.****
If the defect is ADAPTIVE, then log as shown below:
[BRAND ENVIRONMENT BUILD #] [Adaptive Android or iOS] Area
of Defect Description
Defect Summary Examples (please note these are JUST examples)
[DLP - STAGE - 1000] - Resort Listing Page - Empty space after hotels
list]
[DNX - STAGE - 1.52] NL: 'More Help' Menu Link 'Privacy & wettelijke
gegevens' Directs to 404 Error
[DLR/WDW-STAGE-967]Profile | Payment Methods | Add Credit Card is
not being saved
[WDW - ST - 965] Unable To Complete Cart Flow With Tickets Only
Booking
[DLR - ST/PROD] AP Discounts Doesn't Sort Tours By Name

Description: Give a brief explanation of what the issue is, where it occurs,
etc. so if anyone were to open your defect and read the description, they
would know what the issue is. This is a more expanded version of the
summary, the summary is a small to the point area of what the defect
issue/area is, once they open the ticket they will look to the description to
find out more about the issue. This is the area where you will put anything
about the issue that may be useful to the dev.
In the description section please put:
Brief explanation of what the issue is
Conversation ID (see below on how to get the conversation ID)
Services list at the time you logged the defect
Any other perdinent information such as, if it is for multiple brands
(WDW/DLR etc.) or if it is environment specific or in multiple
environments, as you write in the summary you can briefly touch on it
here just as a verification that the devs know
Attachment: Try to ALWAYS attach a screenshot of where the defect is to
help the devs understand what the issue is. If this is a visual issue then take
a screenshot of the page to show what/where the issue is to make it easier
on the devs to understand whats wrong. If you see an error or content issues,
I will attach a screenshot so there is no confusion what I am talking about.
Labels: NOT REQUIRED. DO NOT PUT ANYTHING HERE
Components: Area where the defect was found, the areas are related to
the verticals and helps us filter the defects based on these components. The
most common components used are as follows:

Global+

Finder+

Theme-Cart+: All cart related issues will be assigned this component

Theme-Tickets+: All Ticket related issues will be assigned this

component

Theme-Lodging+: All lodging/special offers related issues will be

assigned this component

Itinerary+

Profile+

Each of these bullet points is a vertical that you can choose as a component,
BUT, these are the generic components, each of these verticals has multiple
components that are more specific to the area, for example if you find a
defect on an attractions detail page, then the defect component is under
Finder+Detail, since it is a detail page. The more specific component choices
are shown above, if what your defect relates to has does not fall under any of
the specific component types for that vertical, then keep it as the generic
component.
Fix Version: as you can see above, it says Current version. That means,
whatever release you are on, whether it is Releae 1.51, Release 1.65 etc. DO
NOT WRITE CURRENT VERSION. When you are testing in Stage AND in Soft
Launch, you will put the current release.
***Please remember: if the defect is in production, DO NOT PUT A
FIX VERSION***
If you found it in a lower environment and checked and found it also
is in PROD, then you still DO NOT put a fix version, even if it is in a
lower environment, if it is in production, DO NOT put a fix version, it
will not be a launch blocker

Priority: You can choose either a 1,2,3 or 4.

Please note: Priority 1,2, or 3 are LAUNCH BLOCKERS for the release
you are assigning it to
The following definitions are used by the UX team for prioritizing their
defects:
o Priority 1 The specified interaction, visual design, or
content is unrecognizable in the implementation. The
Guest would not be able to understand, appreciate, or
use the feature or move forward in the flow. For example:
elements overlap or sit on top of each other; the copy is
unreadable; the size or placement of elements on the
page is completely different than what was specified.
Issues with global or high-visibility/high-traffic elements.
The Guest experience is broken. This is a launch-blocker.
o Priority 2 The implemented interaction, visual design, or
content is substantially different than what was specified
in such a way that it makes the site look unprofessional.
The Guests ability to understand, appreciate, or use the
feature would be compromised. For example: an element
is partially obscured or extends outside the intended
viewable area; disruptive application of different sizes,
colors, fonts, spacing, etc., across like elements;
incorrect content or media for an element or page. Issues
with global or high-visibility/high-traffic elements. The
Guest might be able to get around/through it but it looks
wrong or unprofessional. This is a launch-blocker.
o Priority 3 The implemented interaction, visual design, or
content is visibly different than specified. The Guest
would still be able to understand, appreciate, or use the
feature. For example: awkward breaks in copy; obvious
application of different sizes, colors, fonts, spacing, etc.,
across like elements; incorrectly sized or cropped
images; external copy or media below internal standards.

Its not great but the Guest can get around/through it

without too significant an impact to the experience. Its
up to the team to proceed or hold but should be
prioritized in the backlog and addressed at the soonest
agreed upon sprint.
o Priority 4 There are minor deviations from the specified
interaction, visual design, or content. The Guest might
not even detect the differences. For example: slight
departures from visual styles; pixels off; isolated issues
with words or punctuation; poorly sized or cropped
images. Its not terrible, but should be fixed at some
point in the future.
Steps to Recreate:

Write in such a way that anyone with limited knowledge of the issue
should be able to understand and follow the steps to reproduce the
issue without difficulty. Doing so will facilitate the ability to confidently
validate a fix for an issue they did not personally log thus are less
familiar about.
Provide step by step instructions on how to reproduce the issue
Include URL where defect was found
Include test data (if applicable, such as days you tried making a
reservation if that is related to the defect)
Include test user accounts (if applicable)
Include Actual and Expected Results

Example of one written in JIRA:

Severity:
o Critical The system is down or key application functionality is
unavailable; testing severely limited such that little to no work can be
completed and/or performance tests cannot be run. The Guest's ability
to complete task or user flow will be severely limited such that
experience would be completely blocked from being completed (no
known work around) or performance is degraded to the point where

guest abandonment is a near certainty.

o High Main functionality of the system is broken; testing is
impacted, but can continue with a workaround for testing
purposes. The Guest's ability to complete task or user flow will be
limited such that the experience is blocked from being completed or
performance is degraded such that guest abandonment is likely.
o Medium Nonconformities occur within a function; minimal testing
impact; issue can be resolved after launch. The Guests ability to
complete the task or user flow is not limited in such a way that the
experience cannot be completed. Any performance degradation is an
annoyance, but not likely to result in guest abandonment.
o Low Minor, non-critical or cosmetic problems exist with the
system; little to no impact on testing or Guest experience.

A detailed FAQ for performance defects can be found on the

following Wiki page:
https://wiki.wdpro.wdig.com/display/Tech/Performance+Defec
ts+FAQ

Studio: Assign to a studio based on the area of the defect, see the PEPCOM
technology wiki page for a detailed list of the studios and what they cover
https://wiki.nge.wdig.com/pages/viewpage.action?
title=PEPCOM+Technology+-+Studios&spaceKey=NGE

Type of Defect:
1.
Accessibility: Defects related to special area Eg. Application failing
to provide information for the special people such as Blind/Deaf.

2.
3.
4.

Analytics : No need to use this by Accenture team

Configuration : No need to use this by Accenture team
Content: A defect only affecting copy or media. A defect which
production will fix mainly via CMS and requires no tech or QA to fix.
Example: Add an image to the hero media of a page.
5.
Environment : A defect related to environment issues
6.
Functional : Deviation from the actual functional requirement
7.
Media : Defect related to Finder Vertical
8.
Security : Out of scope for CQA
9.
SEO : SEO stands for Search Engine Optimization - Out of scope for
CQA
10. Technical : A defect observed due to technical failure
The bolded sections are what CQA most commonly uses when logging
defects

WDW Environment: The environment you found the defect in. STAGE/Soft
Launch/ Production are the environments that you will be selecting.
****ALWAYS WHEN WRITING A DEFECT, CHECK TO SEE IF IT IS IN
PRODUCTION, IF IT IS, THEN IT WILL NOT BE A RELEASE BLOCKER****
If your defect is in multiple environments, then HOLD the CONTROL key
(COMMAND if you hav a MAC) and select the various environments that your
defect affects.

Brand: Enter the site you are testing on, WDW for Disneyworld, DLR for
Disneyland, DLP for Disneyland Paris(DLP = DNX), HKDL for Hong Kong
Disneyland, ETC.
Browsers: Whatever you were testing on where you found this defect,
Firefox, Chrome, Internet Explorer (IE), Mobile app is if you are on a device,
etc.
***If you find a defect and you tested in multiple browsers or it is on mobile
AND PC, then after making one selection, HOLD the CONTROL key (HOLD the
COMMAND key if you have a MAC) to then select multiple options
Opened By: Central QA
Acceptance Criteria: input N/A
Epic Link: This is ONLY APPLICABLE to DLP
For DLP we have various epic links that we link JIRA tickets to in order to kep
track of what defects are related to what sites, since DLP is focused primarily
on launching various languages, the epic links to use for the CURRENT DLP
Languages are:
Netherlands(NL): PRO-93633
UK: PRO-93128
FR/IDF: PRO-91558
As new languages come down the pipe for DLP, there will be an epic link to
link your defects to, each language has its own epic link
***Again, DLP is the ONLY brand with epic links, HKDL/DLR/WDW do
NOT use them***
FINALLY,
Once the defect is logged in JIRA, an email should be sent to the Studio with
this information.
To get the Conversation ID:

1. Go to <url-Env>/debug/developers-toggles > Enable

Debug Mode.

2. Get the Conversation ID from the bottom of the page.

Detailed list of Studios:

***(Please note these are what the studios currently cover as of
November 2014, these are subject to change so please look at the
wiki in the above section)***
Studio
PEP
Technology Studio Funk

Vertical
Global

Outlook
Distribution List
#WDPRO PEPCOM
STUDIO FUNK

Track
Global Vertical
Performance and Quality

Studio 54

Tickets

#WDPRO PEPCOM
Studio 54

Studio Atlas

Global

#WDPRO PEPCOM
Studio Atlas

Studio Bang

Lodging

#WDPRO PEPCOM
Studio Bang

Studio
Bedrock(Ser
vice
Platform
Team)

Services

Studio Bravo

Studio
Control
Studio
Crunch

Content

Tickets
Profile

#WDPRO Platform
Team
#WDPRO PEPCOM
Studio Bravo

#WDPRO PEPCOM
Studio Control
Tech team:
#WDPRO PXP Studio
Crunch
Wider team
including business:
#WDPRO
MDX_Vertical_Profile

Tickets store (pre-cart/checkout)

Affilate ticket stores
Product Service (Tickets)
OSDL (Tickets)
Memory Maker Standalone Tickets

Global Personalization (Global I): My Story

Maker
Online Modifications - Lodging
Lodging Sales (Resorts)
Special Offer Sales (co-owned with TNT)
Personalized (PIN) Offer Sales (co-owned with
TNT)
Availability Service (Resorts)
Quick Quote (Lodging Search Form)
Apigee
Bulk Service
Content Service
Expand Service
Hippo CMS
Media Service
Vendomatic UI
Content Entry
Tickets store (pre-cart/checkout)
Affilate ticket stores
Product Service (Tickets)
OSDL (Tickets)
Memory Maker Standalone Tickets
Tickeration/Transfer/Claim
Claim - Annual Passes
Claim - Park Tickets
Claim - MagicBands and RFID cards
Claim - Special Events
Claim - Memory Maker
Profile+ Vertical is Studio Crunch
MDX Sign In, Registration, Forgot Password
MDX Profile and Payment Methods
MDX Family & Friends
MDX Magic bands (service is xBMS team)

Studio
Discovery
Studio
Dragon
Studio Dyno-mite
DevOps

Global

Services

Studio Flash
Studio
Gaucho

Lodging

Studio Green

Tickets

Studio Guest
Studio
Honey
Badgers

Studio
Impossible

Global

Cart

Studio
Kapow
Studio Knock
Studio Magic

#WDPRO DevOps
Team
#WDPRO PEPCOM
Studio Flash
#WDPRO PEPCOM
Studio Gaucho
#WDPRO PEPCOM
Studio Green
#WDPRO Guest
Experience Team
#WDPRO PEPCOM
Studio Honey Badger

Studio Jedi
Studio Kaos

#WDPRO PEPCOM
Studio Discovery
#WDPRO Studio
Dragon

Cart

#WDPRO PEPCOM
STUDIO IMPOSSIBLE

Profile service 3.0 and 2.5

(Claim of magic bands/xbands is owned bySF Krista Betts)
Search (Endeca+FAST)
Help & Support
HKDL Calendars (UI only)

Infrastructure & Developer Services

Day Guest Enrollment & PIN Management
Ground Transportation Landing Page, Rental
Car, Ground Transfer and Flight
Lodging Rooms and Packages, Special Offers
Product Service (Tickets)
OSDL (Tickets)
Analyze Guest/partner feedback to improve
Guest exp.
Integration Test & Automation Testing
GLOBAL VERTICAL
UI+
UI Dependencies
iRules
Bouncefilter
Environment configuration
/api/ module
Homepage
Global Navigation
Global Footer
Syndicated Header
Syndicated Footer
Media Engine
Notifications
Global Messaging

#WDPRO Studio Jedi

Mobile Application Support

#WDPRO PEPCOM
Studio Kaos

Online Mods (Cart+)

#WDPRO PXP Studio

Kapow
#WDPRO PEPCOM
STUDIO KNOCK
#WDPRO PEPCOM

Recently moved to DCL project. Area of Scope

TBD
Trade (Cart+) for travel agents
Photopass

Studio Magic

Studio Mars

Cart

Studio Mate

#WDPRO PEPCOM
Studio Mate

Studio
Monsters

#WDPRO Systems
Engineering

Studio Narf

#WDPRO PXP Studio

Narf

Studio
NorthStar
Studio
Pampa

Studio Ping
Studio Prime

FP+/GFF

Finder and
Dine

Itinerary

Cart
FP+/GFF

Studio Slash

Lodging

Studio
Smack

Lodging

Studio Smile
Studio Splat

FP+/GFF
Itinerary

#WDPRO PEPCOM
Studio NorthStar
#WDPRO PXP Studio
Pampa

#WDPRO PEPCOM
Studio Ping
#WDPRO PEPCOM
Studio Prime
#WDPRO PEPCOM
Studio Slash

#WDPRO PEPCOM
Studio Smack
#WDPRO PEPCOM
Studio Smile
#WDPRO PXP Studio
Splat

Disney PhotoPass+ Redaptive

All Cart+ Sustainment / Performance related
work
PAYMENT AND CHECKOUT Flow (including
Commerce Sign-In), Affiliated Stores,
BOOKING, RECOMMENDATION, PAYMENT, AND
RESERVATION SERVICES (only Resort-related
endpoints) (Co-Owns with studio W00T)
DLP (DNX) Lodging
Orange: DME, Dining, Tickets (for packages)
and Personal Magic
Post Orange: Lodging Rooms/Packages, Trade
(with Slash)
Memory Maker add-on to resort Package res
Infrastructure
Fast Pass + redesign,
DVIC
Finder Vertical
Maps, Mapplication
Calendar
Park Hours
Itinerary + sustainment
OLCI
Finder Detail MENUS
Trade for travel agents
CART UI, Cart Service, List Service, Health
Monitor Service, Additional Payments Page
(post-booking)
Great Food Fast
Tools, Trade/Lodging
Product Service (Packages)
Pricing Service
Lodging Sales (Resorts)
Pricing Service - Lodging
OSDL - Lodging
TDL - Lodging
Resort/Hotels detail pages (WDW, BEACH
RESORT, DLR, HKDL)
Resort/Hotels listing page (WDW, BEACH
RESORT, DLR, HKDL)
FastPass+ (Web-based) Sustainment, GXP
Mobile Service, GXP/FP+ (Xpass)
Itinerary Plus Vertical
MagicBands and Cards

Itinerary Day View

Add to My Plans from Finder
My Reservations My Reservations is now
supported by Studio Atlas
Claim Resort, Dine, and Activity Reservations
Reservation Service (w/Atlas)

Studio
Stereo

Lodging

#WDPRO PEPCOM
STUDIO Stereo

Main Entrance Pass (Cast as Guest)

Lodging vertical
DLP (DNX)
Online mods
Lodging Sales (Resorts)
Special Offer Sales (co-owned with Bang)
Personalized (PIN) Offer Sales (co-owned with
Bang)

Lodging

#WDPRO PEPCOM
Studio TNT

Global

#WDPRO PEPCOM
STUDIO TOPA

Studio
Torque

Finder and
Dine

#WDPRO PEPCOM
Studio Torque

Studio
Triumph

Finder and
Dine

#WDPRO PEPCOM
Studio Triumph

Studio
Victory!

Finder and
Dine

#WDPRO PEPCOM
Studio Victory

Studio W00T
Studio Zap

Services
Finder and
Dine

#WDPRO PEPCOM
Studio W00t
#WDPRO PXP Studio
Zap

Studio TNT

Studio Topa

Availability Service (Resorts)

OSDL (Packages)
GLOBAL VERTICAL
Breadcrumbs
Annual Pass non-sales pages
MDX "Guide Me"
MDX Landing Page
MM+ Custom Pages
Global Messaging
Help & Support
Finder+ Detail Pages (excluding dine
availability module -> Zap)
Finder Service
Facility Service
Review Service
Finder List
All Activities
Wishlist
Online Modifications - CART+
Live Chat (LivePerson)
ANALYTICS for Cart, Cart Service (for Saved
shops), Payment and Checkout, HH/VB
Booking Service
Payment Service
Reservation Service (Resort-specific endpoints
only)
Recommendation Service
Dine Availability & Booking
A vailability Service (Dine)

Booking Service (Dine)

Cart Service (Dine)
Pricing Service (Dine)

Studio Zort

Finder and
Dine

#WDPRO PEPCOM
Studio Zort

Product Service (Dine)

Finder List
All Activities
Wishlist
Finder Details (Sustainment Only)