toco-cam
commented
2 months ago ================ END OF EPIC BODY ================
PLEASE WRITE ANY CONFIDENTIAL INFORMATION IN THE COMMENTS SECTION BELOW. ANY INFORMATION IN THE BODY WILL BECOME PUBLIC AFTER ADDING THE public LABEL.
Breakdown This section links to various sub-issues / -tasks contributing to respective epic phase or phase results where appropriate.
Discovery phase
- Zeiss https://jira.camunda.com/browse/SUPPORT-21344
- Data Group https://jira.camunda.com/browse/SUPPORT-14236
Define phase Design Planning
Reviewed by design: {date} Designer assigned: {Yes, No Design Necessary, or No Designer Available} Assignee: Design Brief - {link to design brief } Research Brief - {link to research brief } Design Deliverables
{Deliverable Name} {Link to GH Issue} Documentation Planning
Risk Management
Assessment: Risk Class: Implement phase Validation Criteria Validate phase Links to additional collateral
Value Proposition Statement
Improve handling and prioritization of alerts in communication tools (Email, Slack, ...).
User Problem
Context
Problem
Without an environment name and process, it is not possible to properly prioritize alerts.
The subject can not be used to route alerts with Email rules \/ or in Slack.
Release Notes
User Stories
Implementation Notes
Solution idea: https://jira.camunda.com/browse/SUPPORT-21344?focusedCommentId=344461&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-344461
The alert subjects should also contain the status of the alert (New - Reminder - Resolution)
:robot: This issue is automatically synced from: source