-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
- Show Tracker Database Check:
- A CS team member checks the Confluence database to see if a show exists.
- If it exists, some updates might be needed.
- If it doesn't exist, the user manually enters the show's information, including tier classification (Tier Max, Tier 0, Tier 1, Tier 2).
- Confluence Page Automation:
- Automatically create a Confluence page based on a pre-existing template, depending on the tier.
- Change the page's name to "Production X" (where X is the production's title from the database).
- Move the page to a folder based on the studio attribute from the database.
- Apply labels across the Atlassian ecosystem based on attributes from the database.
- Jira Automation:
- Automatically create a Jira Epic titled "Production X" using a template Epic, depending on the tier.
- Generate Jira stories, tasks, and sub-tasks mapped to the appropriate task type based on the template Epic.
- Create specific tasks based on tier-related security requirements.
- Risk Management:
- New Confluence pages trigger the creation of Jira tasks, specifically 'CS Risk' tasks.
- Add these risks to an overall risk register page and a show-specific risk register embedded in the new page, using custom JQL queries.
- Automatically generate JSM tickets from 'CS Risk' tasks, ensuring one-to-one mapping and synchronization.
- Notifications:
- Notify the CS team via email and Slack/MS Teams when 'CS Risk' tasks are created.
- If a show in the database moves from Development to Prep and is tagged as Tier Max or Tier 0, send an email to the site security team.
- relates to
-
- Under Consideration