Skip to content
Notis

Get repository context for every new Jira issue

Start new work with a clear view of where it may touch the codebase. Devin can answer a focused repository question when a Jira issue arrives.

Trigger

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

Action

Ask question

Ask any question about a GitHub repository and get an AI-powered, context-grounded response. Args: repoName: GitHub repository or list of repositories (max 10) in owner/repo format question: The question to ask about the repository

Why this helps

A fresh ticket can mean a context switch into unfamiliar code before anyone knows where to begin.

  • Surface likely code areas sooner
  • Reduce manual repository searches
  • Give the assignee a useful starting point

Setup

Build it in a few focused steps.

  • 1Connect Jira and Devin MCP once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name.
  • 3Describe the outcome in one instruction, such as asking Devin to investigate the repository context for each new issue.
  • 4Pick Jira New Issue as the trigger and choose where run reports should go.
  • 5Test with one real issue and confirm the repository question has enough context.

Questions about this workflow

What does this automation do?

It uses Devin MCP to ask a repository question when Jira creates an issue, then reports the response through Notis.

Does it know which repository the issue belongs to?

The action needs a GitHub repository name in owner/repo format. Include how to identify the repository in your instruction or supply it when needed.

Will it update the Jira issue?

No. The available Devin actions answer questions or read repository documentation; this workflow reports findings without editing Jira.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to Devin MCP. A trigger fires from one place; an action lands in another.

Jira triggers

Devin MCP actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Ask question

Ask any question about a GitHub repository and get an AI-powered, context-grounded response. Args: repoName: GitHub repository or list of repositories (max 10) in owner/repo format question: The question to ask about the repository

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

List available repos

List all repositories available to query with your Devin account. Only available in private mode (via devin.ai endpoints).

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Read wiki contents

View documentation about a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Read wiki structure

Get a list of documentation topics for a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Connect any two apps with Notis in the middle.

Jira and Devin MCP, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Devin MCP.