Keep Jira release tickets aligned with Appveyor status
Bring deployment status back to the Jira release work on a regular cadence, with less manual checking and updating.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
Release tickets can become stale when build and deployment progress changes faster than someone remembers to update Jira.
- Keep release work informed by current deployment details.
- Reduce manual ticket maintenance during release coordination.
- Make status changes easier to find in the team's source of work.
Setup
Build it in a few focused steps.
- 1Connect Appveyor and Jira once in the Notis portal.
- 2Create an automation from Automations, New Automation, or tell Notis the outcome in plain language from any channel.
- 3In one instruction, ask Notis to review available Appveyor deployment status and update the matching Jira release issue with the current details.
- 4Choose the recurring schedule trigger and select where run reports should go.
- 5Test with one real deployment and its related Jira release issue.
Questions about this workflow
What does the Jira issue need to contain?
Notis needs enough identifying context in the available build data or your instruction to locate the related release issue.
What information can be added?
The automation can use deployment status and build details available from Appveyor. Name the specific status information you want reflected in the Jira issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Appveyor to Jira. A trigger fires from one place; an action lands in another.
Appveyor triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Appveyor and Jira, 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 Jira.