---
title: "Jira Task Helper recipe for Slack and Telegram | Agent Barn"
canonical: "https://agentbarn.dev/recipes/jira-task-helper/platform"
updatedDate: "2026-08-29T16:41:32.000Z"
author: Agent Barn
description: Turns a plain-language request into a structured Jira task and files it for the team. Set it up on Slack or Telegram with Agent Barn.
tags: [Work intake, AI agents, workflow automation]
categories: [Recipes]
---

# Jira Task Helper recipe for Slack and Telegram

A work-intake teammate that helps a team capture requests consistently without turning every message into manual ticket triage.

## Choose a platform

### Slack

**Shared intake channel.** Turns requests posted by anyone in the channel into structured issues, with the resulting ticket visible to the whole team.

Choose when requests arrive from several people and the team tracks them together.

### Telegram

**One requester.** Files issues from a single chat, so one person captures work as it comes up without opening Jira.

Choose when one person raises the tickets and no shared intake queue is needed.

## Recipe overview

- Category: Work intake
- Tools: Jira + Slack
- Trigger: A teammate submits a request in an allowed Slack channel or direct message.

## Workflow

1. **Read request:** Collect the request and its available context.
2. **Structure work:** Prepare the title, description, and required task fields.
3. **Check gaps:** Ask for missing information when the configured workflow requires it.
4. **File task:** Create the Jira item and return its link to Slack.

## Initial setup

1. **Template:** The project-specific intake questions and ticket format.
2. **Skills:** Jira access and the actions permitted in the connected project.
3. **Policies:** Where intake is allowed and who can request ticket creation.

## Integrations

### Jira

Read project metadata and create structured issues in approved projects.

- Requirement: required
- Credential: An Atlassian account email, site URL, and scoped or non-scoped API token.

#### Permissions

- Projects: browse
- Issues: create
- Comments: add only when follow-up requires it

#### Setup

1. Choose the target project and allowed issue types.
2. Map required fields, components, and labels before launch.
3. Create a test issue and verify the agent cannot write to projects outside scope.

## Human review

Use project-specific required fields and keep any consequential prioritization or assignment with the responsible team.