Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jira Integration: Add project_override similar to slack's channel_override #1659

Open
ivankovnatsky opened this issue Dec 11, 2024 · 1 comment

Comments

@ivankovnatsky
Copy link
Contributor

Is your feature request related to a problem?

I think it's more or less self explanatory, but to reiterate, we want to route the Jira issue creation into specific team's Jira projects.

Describe the solution you'd like

Similar to what slack sink has with it's channel_override.

Describe alternatives you've considered

Create separate Jira project and issue type for specific robusta jira alerts.

Additional context

Consider this config example:

clusterName: 
sinksConfig:
  - robusta_sink:
      name: robusta_ui_sink
      token: 
  - slack_sink:
      name: prod_infra_alerts
      slack_channel: 
      channel_override: "${labels.app.owner}-prod"
      api_key: 
      match:
        severity: [LOW, MEDIUM, HIGH]
...
  - jira_sink:
      name: 
      url: 
      username: 
      api_key: 
      dedups:
        - fingerprint
      project_override: "${labels.app.jira_project}"
      issue_type: 
      priority_mapping:
        HIGH: "High"
        MEDIUM: "Medium"
        LOW: "Low"
        INFO: "Lowest"
      match:
        severity: [LOW, MEDIUM, HIGH]
...
Copy link

Hi 👋, thanks for opening an issue! Please note, it may take some time for us to respond, but we'll get back to you as soon as we can!

  • 💬 Slack Community: Join Robusta team and other contributors on Slack here.
  • 📖 Docs: Find our documentation here.
  • 🎥 YouTube Channel: Watch our videos here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant