Is your improvement proposal related to a problem? Please describe.
Currently, Slack integration notifications are often limited to general channel-wide updates. For long-running pipelines (e.g., those exceeding 15 minutes), developers frequently switch contexts, leading to delays in reacting to successful or failed builds.
There is a need for more granular, user-centric notification logic that targets the specific author of a Pull Request or the individual who triggered a job. The goal is to move beyond general filters and provide a personalized feedback loop.
Key Requirements:
- Direct Mention: Ability to notify the specific PR author or job initiator in Slack rather than just posting to a shared channel.
- Extended Filtering: More robust subscription options that allow individuals to opt-in to events relevant only to their own commits or specific pipeline outcomes.
- Context Retention: Helping developers maintain workflow momentum by providing immediate, personalized status updates after long execution periods.
Describe the solution you'd like
TBD
Describe alternatives you've considered
No response
Additional context
No response
Is your improvement proposal related to a problem? Please describe.
Currently, Slack integration notifications are often limited to general channel-wide updates. For long-running pipelines (e.g., those exceeding 15 minutes), developers frequently switch contexts, leading to delays in reacting to successful or failed builds.
There is a need for more granular, user-centric notification logic that targets the specific author of a Pull Request or the individual who triggered a job. The goal is to move beyond general filters and provide a personalized feedback loop.
Key Requirements:
Describe the solution you'd like
TBD
Describe alternatives you've considered
No response
Additional context
No response