See Codacy organization repositories when Jira work starts
A new issue is easier to route when the related codebase is visible. Ask Notis to retrieve the repositories available under your chosen Codacy organization and provider.
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
Get Organization Repositories
Tool to list all repositories under a specific organization and provider. use when you need to enumerate organization-scoped repositories.
Why this helps
Finding the right codebase across an organization can add manual steps before a new issue is ready for action.
- Brings organization repository options into the issue run report
- Reduces the effort of manually scanning for likely codebases
- Makes repository discovery repeatable for new work
Setup
Build it in a few focused steps.
- 1Connect Jira and Codacy once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for repository discovery.
- 3Describe the outcome in one instruction: when a Jira issue is created, list repositories under the relevant Codacy organization and provider.
- 4Pick the Jira New Issue trigger and choose where run reports should go.
- 5Test with one real issue and confirm the organization repository list appears in the report.
Questions about this workflow
Will this analyze the listed repositories?
No. The action lists organization repositories; it does not analyze their code.
Does the action choose an organization and provider automatically?
The action requires a specific organization and provider. Include the applicable choices in your instruction; do not expect Notis to invent them.
Can it infer the exact repository from issue text?
It may help compare available repository names with issue context, but report uncertainty if the issue lacks enough detail.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Codacy. A trigger fires from one place; an action lands in another.
Jira triggers
Codacy actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create API Token
Tool to create a new api token for the authenticated user's account. use after authenticating when you need to generate a fresh token for integrations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete API Token
Tool to delete a specific api token from the authenticated user's account. use after confirming the token id.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Get Account Details
Tool to retrieve details of the authenticated user's account. use when confirming authentication before user-level operations.
New Project
Triggered when a new project is added in Jira
Get Organization Repositories
Tool to list all repositories under a specific organization and provider. use when you need to enumerate organization-scoped repositories.
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.
Get User Organizations
Tool to list all organizations the authenticated user belongs to. use after authenticating and need to discover accessible organizations.
List Projects
Tool to list all projects accessible to the authenticated user. use when you need a list of repositories after confirming api token validity.
Connect any two apps with Notis in the middle.
Jira and Codacy, 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 Codacy.