Frontend School

Jira Service Management Incident Map

Machine Coding
medium

Jira Service Management Incident Map

Medium
React
TypeScript
UI
Map
Markers
Data Visualization

Overview

At Atlassian, our Jira Service Management product helps teams respond to incidents quickly and efficiently. For large organizations, incidents can occur across various geographical locations, affecting different services. Visualizing these incidents on a map provides operations teams with a crucial birds-eye view, enabling faster triage and resource allocation. This problem challenges you to build a simplified incident map viewer.

What you need to do / Task

Your goal is to build a React application that displays a list of simulated incidents on an interactive map.

  1. Map Initialization: Render an interactive map centered on a reasonable default location (e.g., a central point covering the mock data).
  2. Incident Markers: Display each incident from the provided mock data as a distinct marker on the map.
  3. Marker Details: When a user clicks on an incident marker, a small pop-up or tooltip should appear, displaying key details of that incident (e.g., id, description, severity).
  4. Severity Filtering: Implement a mechanism (e.g., checkboxes, buttons) that allows users to filter incidents by their severity (Critical, Major, Minor). When a severity is deselected, incidents of that type should disappear from the map.

UI/UX expectations

  • The map should be the primary focus, occupying a significant portion of the screen.
  • Markers should be visually distinct, potentially indicating severity (e.g., different colors or icons, though simple default markers are acceptable if time is tight).
  • Filtering controls should be easily accessible, perhaps in a sidebar or a control panel above the map.
  • The incident detail pop-up should be concise and clearly present the information.
  • Basic responsiveness is a plus, ensuring the layout adapts reasonably to different screen sizes.

Acceptance criteria

  • An interactive map is rendered and displayed.
  • All incidents from the mock data are initially displayed as markers on the map.
  • Clicking any incident marker opens a pop-up showing its id, description, and severity.
  • Users can toggle the visibility of 'Critical', 'Major', and 'Minor' incidents independently.
  • When a severity filter is applied, only incidents matching the selected severities remain visible on the map.
  • Deselecting all severities should result in no markers being visible.

Constraints

Constraints & assumptions

  • You must use React with TypeScript.
  • The application should be purely client-side; no backend integration is required.
  • All incident data will be provided as mock data within the App.tsx file.
  • You are encouraged to use a map library like react-leaflet for map rendering and marker management. Relevant dependencies (react-leaflet, leaflet) are pre-configured.
  • Focus on functionality and clean code over pixel-perfect design.

Out of scope

  • Implementing search functionality for incidents.
  • Creating custom marker icons beyond basic color/shape variations (unless simple with react-leaflet).
  • Advanced map features like drawing tools, heatmaps, or routing.
  • Persisting filter selections across sessions.
  • Extensive error handling or loading states.

What interviewers evaluate

  • Technical Proficiency: Correct and idiomatic use of React, TypeScript, and the chosen map library.
  • Problem Solving: Ability to break down the problem, manage state effectively, and implement filtering logic.
  • Code Quality: Readability, maintainability, and organization of the codebase.
  • User Experience: Thoughtful consideration of UI/UX, ensuring the application is intuitive and functional.

Loading editor...