Jira | Marketing Operations (Next Gen)

The page houses all content on MOPS Jira process as it pertains to website requests, coupon codes, sunsets, and more.

Our MOPS Jira Board

Request categories 

  • edX.org Website Requests – new page creation, existing page edits, retirements or sunsets
  • Marketing Operations Support – mainly related to HubSpot requests 
  • Coupon codes – (2U employee requests for Enrollment Codes Only)
  • Marketing Reports – report requests
  • Legacy Marketing Operations Support – [B2B Sales] – new client branded rage requests, paid lead generation requests
  • Deprecated Request Categories – email requests [Email Team], existing copy writing updates, new copy writing request

I created the section for Coupon Codes – (2U employee requests for Enrollment Codes). It’s actually the least used way of coupon code requests but that is mainly because people in our company rarely need to request enrollment codes, specifically..  That’s for reasons that we can cover in my coupon codes training. 

JIRA Flow chart for tickets based on Sunsets

General Process

This outlines the steps taken to determine and execute what is needed for each sunset in managing the process in Jira (including creating ticket and all associated requests).

  • MOPS notified of need for Retirement/Sunset and timeline.
  • Day one – Set-up tickets (with due dates aligned to timeline) for:
  • Later (or less urgently) – Set-up further tickets
    • Catalog management ticket – ticket filed to MOPS to pull down about page (AFTER redirect implemented) and set active status(es) to retired/unpublished (completed after CR is complete) – Set ticket as blocked by redirect ticket.
    • NOTE – this ticket is created after the redirect ticket is created, but the work occurs after the redirect itself is completed. 
      • Need UUID
    • Coupon generation – ticket filed to MOPS to generate coupon codes for programs with active entitlements (completed as defined in retirement tracker doc)
    • Link Tickets based on project and deadline
      • There could be 4-5 tickets, one for each part of the process
      • In cases of deadlines that dictate the work on individual processes (ex: De Merchandise or Redirects) be done after differing times, create separate versions of the process for the differing deadlines and be sure they are linked to the main ticket.

Product Types

Meta Data and Redirect priority list for each product type that we sunset:

OC Courses

Most courses will not go through a sunset/retirement process unless specifically requested. 

Redirect to:

  • Institution page
  • Primary Subject (/learn) page

Ideal Ticket Metadata:

  • Course Name / Number
  • UUID
  • About page URL
  • Redirect URL
  • Cross-link to requesting ticket

OC Programs

Redirect to:

  • Product line container page
    • https://www.edx.org/certificates for Professional Certificates
    • https://www.edx.org/masters/micromasters for MicroMasters Programs
    • https://www.edx.org/bachelors/microbachelors for MicroBachelors Programs
    • https://www.edx.org/xseries for XSeries programs

Ticket Metadata:

  • Program Name & Offering Institution
  • UUID
  • About page URL
  • Redirect URL
  • Link to Retirement Tracker
  • Cross-link to requesting ticket

Executive Education

Exec Ed is managed from the GetSmarter side via GEAG. Most will not go through a sunset/retirement process unless specifically requested. There should be no catalog management tasks associated with EE sunsets/retirements, but redirects and de-merchandising may be necessary.

Redirect to:

  • to the subject-specific product landing page for the primary subject retiring product (e.g. https://www.edx.org/executive-education/digital-transformation for a retiring Digital Transformation program)
  • To the product line container page if there are no more products under the subject vertical (e.g. https://www.edx.org/executive-education/)

Ticket Metadata:

  • Program Name & Offering Institution
  • UUID
  • About page URL
  • Redirect URL
  • Cross-link to requesting ticket

Degrees, (Bachelor’s, Master’s, PHD’s & some Certificates)

Redirect to:

  • the subject-specific product landing page for the primary subject retiring product (e.g. https://www.edx.org/masters/online-mba for a retiring MBA Degree)
  • to the product line page if there are no more products under the subject vertical or if the subject vertical page doesn’t exist
    • https://www.edx.org/masters
    • https://www.edx.org/bachelors
    • https://www.edx.org/doctorate   

Ticket Metadata:

  • Short Code (if available)
  • Program Name & Offering Institution
  • UUID
  • About page URL
  • Redirect URL
  • Cross-link to requesting ticket

Partnerships (School/Institutions)

Redirect to:

  • edx.org 

Ticket Metadata:

  • Partner Name
  • XMoniker
  • UUID
  • About page URL
  • Redirect URL
  • Cross-link to requesting ticket

Resources