Bring repository documentation into Jira issue updates
A ticket change can alter what the team needs to know. Pull the repository's existing wiki contents into a Notis run report for quick reference.
Trigger
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.
Action
Read wiki contents
View documentation about a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")
Why this helps
Important repository guidance is easy to miss when the ticket changes and documentation lives elsewhere.
- Make existing repository guidance easier to find
- Reduce time spent switching between ticket and docs
- Give the team a consistent documentation reference
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 name it for its documentation outcome.
- 3Describe in one instruction which repository wiki contents should be retrieved when a Jira issue changes.
- 4Pick Jira Updated Issue as the trigger and choose where run reports should go.
- 5Test with one real issue update and confirm the repository and wiki context are available.
Questions about this workflow
What does Devin return?
The selected action reads wiki contents for a GitHub repository specified in owner/repo format.
Does the trigger run for comment changes?
The Jira Updated Issue event does not fire on comment activity. It fires when an issue field changes in the configured project.
Can it tell which pages relate to the changed field?
The action reads repository wiki contents. If you need a focused result, describe the issue context and documentation question in your instruction; unavailable context must be supplied.
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.
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
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List available repos
List all repositories available to query with your Devin account. Only available in private mode (via devin.ai endpoints).
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Read wiki contents
View documentation about a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")
New Project
Triggered when a new project is added in Jira
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")
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.
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.