Keep ClassMarker subcategories aligned with Jira taxonomy changes
Carry approved category adjustments into ClassMarker while the Jira change is still in view.
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 Sub-Category
Tool to update an existing sub-category. Use when you need to rename or move a sub-category after confirming its IDs.
Why this helps
Taxonomy changes can be approved in Jira and then missed in the question bank.
- Connect taxonomy requests with the resulting category update.
- Avoid relying on memory to apply approved changes.
- Flag missing category identifiers for resolution.
Setup
Build it in a few focused steps.
- 1Connect Jira and ClassMarker once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3Tell Notis to update a ClassMarker subcategory only when the issue identifies the subcategory, parent category, and requested change.
- 4Pick Jira's Updated Issue trigger for the project where taxonomy changes are tracked.
- 5Choose where run reports go, then test with one real taxonomy issue.
Questions about this workflow
What if the issue does not include category IDs?
The action needs confirmed category identifiers. Ask Notis to report the missing IDs instead of guessing.
Will comments trigger the automation?
No. The provided Updated Issue trigger does not fire on comment activity.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Classmarker. A trigger fires from one place; an action lands in another.
Jira triggers
Classmarker actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Access List Item
Tool to add one or more access codes to an access list. Use after obtaining a valid access_list_id to grant exam access.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a new question category
Tool to create a new question category. Use after confirming the parent category 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.
Create Group
Tool to create a new group. Use when you need to organize users into a specific group after planning your user structure.
New Project
Triggered when a new project is added in Jira
Create Question
Tool to create a new question with specified text, type, and category. Use after finalizing details. Set verify_only=True to validate without creating.
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 ClassMarker User
Tool to create a new user in ClassMarker. Use after gathering user details to provision accounts. Provide user info and optional group assignments. Returns the complete API response.
Delete Access List Item
Tool to delete one or more codes from an access list. Use after confirming the list exists.
Delete API Key
Tool to delete an API key by its ID. Use when you need to revoke an API key immediately.
Delete Group
Tool to delete a group by its ID. Use when you need to remove a group from ClassMarker.
Connect any two apps with Notis in the middle.
Jira and Classmarker, 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 Classmarker.