Skip to content

WIP: Add emoji-based Jira issue creation from Slack threads#4940

Open
deepsm007 wants to merge 1 commit intoopenshift:mainfrom
deepsm007:jira-slack
Open

WIP: Add emoji-based Jira issue creation from Slack threads#4940
deepsm007 wants to merge 1 commit intoopenshift:mainfrom
deepsm007:jira-slack

Conversation

@deepsm007
Copy link
Contributor

@deepsm007 deepsm007 commented Feb 11, 2026

This implements Phase 1 of the Slack-Jira integration. Users can now add the :open_jira_dptp: emoji to a thread in #forum-ocp-testplatform to automatically create a Jira issue from that thread.

The implementation includes:

  • Reaction handler that listens for the open_jira_dptp emoji
  • Authorization check to ensure only testplatform team members can use it
  • Thread content fetching with proper pagination
  • Shadowbot summary extraction with fallback to simple concatenation
  • Jira issue creation using existing FileIssue interface
  • ConfigMap storage to track thread-to-Jira mappings and prevent duplicates
  • Confirmation messages posted back to the Slack thread

The code follows the same patterns as the existing FAQ handler and integrates cleanly with the existing Slack bot infrastructure.

/cc @Prucek

This implements Phase 1 of the Slack-Jira integration. Users can now
add the :open_jira_dptp: emoji to a thread in #forum-ocp-testplatform
to automatically create a Jira issue from that thread.

The implementation includes:
- Reaction handler that listens for the open_jira_dptp emoji
- Authorization check to ensure only testplatform team members can use it
- Thread content fetching with proper pagination
- Shadowbot summary extraction with fallback to simple concatenation
- Jira issue creation using existing FileIssue interface
- ConfigMap storage to track thread-to-Jira mappings and prevent duplicates
- Confirmation messages posted back to the Slack thread

The code follows the same patterns as the existing FAQ handler and
integrates cleanly with the existing Slack bot infrastructure.
@openshift-ci-robot
Copy link
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

@coderabbitai
Copy link

coderabbitai bot commented Feb 11, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 11, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepsm007

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 11, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2026

@deepsm007: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/images dfc440b link true /test images
ci/prow/codegen dfc440b link true /test codegen
ci/prow/format dfc440b link true /test format
ci/prow/lint dfc440b link true /test lint
ci/prow/breaking-changes dfc440b link false /test breaking-changes

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants