Keep Blazemeter test details current when Jira issues change
Let Jira updates prompt the Blazemeter test changes your team has specified.
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
Update Test
Tool to update details of a specific test by its id. use when you need to modify test configuration or name of an existing test after confirming its id. example: "update the test name to 'loadtest' for test with id '12345'."
Why this helps
A test can drift from its Jira request when scope or test details change and nobody remembers to update both tools.
- Reduce manual checking for changes to test requests.
- Use issue context to explain requested test changes.
- Get unresolved test references surfaced for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Jira and Blazemeter once in the Notis portal.
- 2Create an automation in the portal or tell Notis to create one from any channel.
- 3In one instruction, ask Notis to update the referenced Blazemeter test when a Jira issue changes, following the change described in the issue and reporting missing test IDs or unclear instructions.
- 4Choose the Jira Updated Issue trigger for the project you want to monitor.
- 5Choose a report channel and test with one real issue update.
Questions about this workflow
How does Notis know which Blazemeter test to update?
The Jira issue or your instruction needs to provide a usable test ID or reference. If it is missing, have Notis report that rather than guess.
Will a Jira comment trigger this?
No. The Updated Issue event does not fire on comment activity.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Blazemeter. A trigger fires from one place; an action lands in another.
Jira triggers
Blazemeter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create API Monitoring Schedule
Tool to create a new schedule for running api monitoring tests. use when you need to automate test runs at defined intervals after determining the correct cron expression and test or collection id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Multi Test
Tool to create a new multi-test within a specified project. use after confirming the project id. example: "create a multi-test named 'load-test' in project 12345."
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 Project
Tool to create a new project. use when you need to initialize a project in a specific workspace. use after confirming the workspace id.
New Project
Triggered when a new project is added in Jira
Create Test
Tool to create a new single test within a specified project. use when registering a new performance test via api.
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.
Delete API Monitoring Schedule
Tool to delete a specific test schedule by its id. use when you need to remove a scheduled test by its unique schedule identifier.
Get Accounts
Tool to retrieve a list of accounts associated with the authenticated user. use after confirming valid authentication.
Get API Monitoring Schedule
Tool to retrieve details of a specific api monitoring schedule by its id. use when you need to inspect the configuration or timing of an existing schedule.
Get API Monitoring Schedules
Tool to retrieve a list of all test schedules in your account. use when you need to enumerate existing schedules to manage or review them.
Connect any two apps with Notis in the middle.
Jira and Blazemeter, 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 Blazemeter.