Keep ClassMarker parent categories aligned with Jira
Bring approved category changes into your question bank with the right category details attached.
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 an existing parent category
Tool to update an existing parent category. Use after confirming the parent category ID.
Why this helps
Parent category changes can be approved in Jira but left unfinished in ClassMarker.
- Carry approved parent category changes into ClassMarker.
- Keep the requested change tied to its Jira issue.
- Catch missing identifiers before an update is attempted.
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 parent category only when the issue identifies its category ID and the 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 parent category change.
Questions about this workflow
Can this rename and move categories?
The action updates an existing parent category. State the intended change in the Jira issue and provide the confirmed category ID.
What happens if the issue is missing details?
Instruct Notis to report what is missing for review rather than guessing.
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.