linkedin / linkedin/iris

highlight incidents with failed 3rdparty delivery status in incident view

Open
#214 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
845
Forks
146
PR merge metrics
No merged PRs in 30d

Description

so that users don't have to click into the detailed message view to check the twilio delivery status.

bonus point: have a per incident stats summary including success rate and some other interesting data.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the incident view and the detailed message view, then trace where the Twilio delivery status is exposed for messages. Define the incident-level status display first; treat the per-incident success-rate and additional statistics as separate scope that needs clarification before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.