Connect new Jira issues to your Codacy project list
A new Jira issue can start a code task. Ask Notis to check your available Codacy projects and reduce the time spent hunting for the right repository.
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
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.
Why this helps
Issue triage often stalls while someone searches for the repository that owns the code change.
- Cuts manual repository hunting during issue triage
- Keeps the project lookup connected to the issue that prompted it
- Helps the team confirm which Codacy projects are accessible
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 give it a clear name.
- 3Describe the outcome in one instruction: when an issue is created, list accessible Codacy projects to help identify the related repository.
- 4Pick the Jira New Issue trigger and choose where run reports should go.
- 5Test with one real Jira issue and review the Codacy project list in the run report.
Questions about this workflow
Does this workflow analyze the code for the issue?
No. The available Codacy action lists projects accessible to the authenticated user. It does not run an analysis or review code.
Will it check every Jira project?
No. The Jira New Issue event fires only for the Jira project configured for that trigger.
Can Notis identify the exact repository from the issue?
Only if the issue provides enough context and the returned project data can be compared. If repository details are missing, ask Notis to report that uncertainty.
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.