Start code review from a new Jira issue
Turn a tracked Jira request into a Bitbucket pull request when its source branch is ready.
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
Create a pull request
Creates a new pull request in a specified bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
Why this helps
Teams can lose time translating approved Jira work into the first code review step.
- Reduce manual handoff from planning to review
- Put Jira context into the review request
- Create a consistent starting point for code review
Setup
Build it in a few focused steps.
- 1Connect Jira and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to create a pull request for a new Jira issue using an already available source branch and suitable destination branch.
- 4Pick the Jira New Issue trigger and choose where run reports should go.
- 5Test with one real issue and an existing source branch.
Questions about this workflow
Does this create a source branch too?
No. This action creates a pull request and requires that the source branch already exists.
What if the branch or destination is unknown?
Supply a reliable branch rule in the instruction. If Notis cannot determine a valid existing source branch, the pull request cannot be created.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Bitbucket. A trigger fires from one place; an action lands in another.
Jira triggers
Bitbucket actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a branch
Creates a new branch in a bitbucket repository from a target commit hash; the branch name must be unique, adhere to bitbucket's naming conventions, and not include the 'refs/heads/' prefix.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create an issue
Creates a new issue in a bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component ids exist.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
New Project
Triggered when a new project is added in Jira
Create a pull request
Creates a new pull request in a specified bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
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.
Create repository
Creates a new bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if `project key` is not provided.
Create snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
Delete issue
Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.
Delete repository
Permanently deletes a specified bitbucket repository; this action is irreversible and does not affect forks.
Connect any two apps with Notis in the middle.
Jira and Bitbucket, 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 Bitbucket.