Adding Issue ID followed by Short Description of Event to notification subject lines for all Notifications - Issue Resolution Service

✅ Why this enhancement is useful

Adding the Issue ID in the subject line makes notifications:

• Immediately actionable – users can identify the exact issue without opening the email

• Searchable & trackable – enables quick retrieval in Outlook using Issue ID (e.g., QGC-TQ-00091)

• Context-rich – eliminates ambiguity when multiple issues are being handled simultaneously

In large-scale projects, where:

• Hundreds of issues may be active at once

• Multiple stakeholders interact across disciplines, regions, and systems

• Email remains a primary communication channel

👉 This small change significantly improves clarity, traceability, and response time

👥 Who benefits

⚙️ How it should work (Recommended behaviour)

• Every notification subject should follow a standardized format:

[Issue ID] – [Short Description of Event]

Example:

• ✅ QGC-TQ-00091 – The status of an issue has changed

• ✅ QGC-TQ-00091 – Issue assigned to you has changed

• ✅ QGC-TQ-00091 – Issue moved to Review Process – LFE

Key principles:

• Issue ID always first → ensures visibility in inbox preview

• Consistent format across all notifications

• Event description kept short and standardized

2. Example Scenario (Realistic Project Use Case)

Scenario: Multi-discipline Design Review Cycle

• An EPC contractor raises multiple Technical Queries (TQs):

  • QGC-TQ-00091 (Electrical)

  • QGC-TQ-00102 (Mechanical)

  • QGC-TQ-00115 (Instrumentation)

• A Document Reviewer receives 10–15 notifications/day across disciplines.

❌ Current state (without Issue ID in subject)

• Subject: “The status of an issue assigned to you has changed”

• User must:

  • Open each email

  • Read content

  • Identify Issue ID

  • Decide relevance

⏱ Time wasted per email: ~10–20 seconds

✅ With enhancement

• Subject:
  QGC-TQ-00091 – The status of an issue has changed

• User can:

  • Instantly recognize relevance

  • Prioritize critical issues (e.g., high-risk discipline)

  • Use Outlook rules / search filters (e.g., filter "QGC-TQ-00091")

👉 Result:

• Near zero effort identification

• Faster decision-making in high-volume environments

3. Cost of NOT implementing this

⏱ Time Impact

• Users must open every email to identify relevance

• For high-volume users (~50 notifications/day):

  • ~10 seconds extra per email

  • = ~8–10 minutes/day wasted per person

  • Across project teams → significant cumulative loss

📉 Quality Impact

• Increased risk of:

  • Missing critical issues

  • Delayed responses

  • Miscommunication across stakeholders

🔁 Operational Overheads

• More dependency on:

  • Manual tracking (Excel trackers, logs)

  • Re-checking emails

  • Follow-up communications

• Increased support load on System Admin teams:

  • “Which issue is this notification for?”

  • “Can you resend link / details?”

💰 Business Impact (High-level)

• Delays in issue closure → potential project schedule slippage

• Reduced efficiency in review cycles

• Lower productivity across distributed teams

Summary:

Adding Issue ID to notification subject lines is a low-effort, high-impact improvement that enhances traceability, prioritisation, and operational efficiency across complex oil & gas project workflows.