Bring Appveyor build artifacts into Jira follow-up
When issue details change, retrieve artifacts from the related Appveyor job to make build outputs easier to find during follow-up.
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
Get Build Artifacts
Tool to get the list of artifacts for a specific build job. use when you need to retrieve artifacts after a job completes.
Why this helps
Build outputs can be hard to locate while following an updated Jira issue, especially when the relevant build job is buried in another tool.
- Retrieve artifacts when a Jira issue changes.
- Keep relevant build outputs close to issue follow-up.
- Avoid manually searching Appveyor when the job identifier is known.
Setup
Build it in a few focused steps.
- 1Connect Jira and Appveyor once in the Notis portal.
- 2Create an automation in the portal or from any channel.
- 3In one instruction, ask Notis to retrieve artifacts for the related Appveyor job when the build identifier is available.
- 4Pick the Jira Updated Issue trigger and choose where run reports go.
- 5Test with one real updated issue that includes or identifies its Appveyor build job.
Questions about this workflow
What information is needed to retrieve artifacts?
The action needs a specific Appveyor build job. Supply its identifier in the issue context or in the automation instruction.
Do Jira comment changes trigger this automation?
No. The Updated Issue event does not fire for comment activity.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Appveyor. A trigger fires from one place; an action lands in another.
Jira triggers
Appveyor actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Build Artifacts
Tool to get the list of artifacts for a specific build job. use when you need to retrieve artifacts after a job completes.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Environments
Tool to get a list of all deployment environments. use when you need to enumerate available environments before creating deployments.
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 Projects
Tool to get a list of all projects for the authenticated account. use after authentication to enumerate available projects.
New Project
Triggered when a new project is added in Jira
Get Role
Tool to retrieve details of a specific role. use when you need to inspect permissions and metadata of a role by id.
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 Roles
Tool to retrieve all roles in the account. use when you need to enumerate available roles before assigning permissions.
Get Users
Tool to retrieve all users in the account. use when you need to list all team users in your appveyor account.
Connect any two apps with Notis in the middle.
Jira and Appveyor, 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 Appveyor.