Keep a compact record of Jira issue changes
When Jira changes an issue, update its corresponding Hive entry with the latest details available from the event.
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
Map Put
Tool to set or update key-value pairs in a hive map. use when you need to add or update multiple entries in a hive map.
Why this helps
A separate record of work can drift out of date after issue changes.
- Reduce stale duplicate records
- Keep issue references in one Backendless map
- Make updates easier to find later
Setup
Build it in a few focused steps.
- 1Connect Jira and Backendless once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3In one instruction, ask Notis to update the matching Hive map entry with the latest issue details available.
- 4Pick Jira Updated Issue as the trigger and choose where run reports should go.
- 5Test with one real issue update and review the run report.
Questions about this workflow
Can this update an existing Hive entry?
Instruct Notis how to identify the matching entry, and confirm the required issue identifier and Hive key are available.
Does the event include comment changes?
No. Comment activity does not trigger Jira Updated Issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Backendless. A trigger fires from one place; an action lands in another.
Jira triggers
Backendless actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Copy File
Tool to copy a file or directory within backendless file storage. use when duplicating files to a new location after verifying source and destination paths.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Directory
Tool to create a new directory at the specified path. use when you need to organize files under a new folder structure.
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 Backendless Hive
Tool to create a new hive. use when you need to provision a new hive resource before performing hive operations. example: create a hive named 'grocerystore'.
New Project
Triggered when a new project is added in Jira
Create Backendless Timer
Tool to create a new timer with schedule and code. use when scheduling recurring or one-off tasks to run server-side logic after confirming parameters.
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 Directory
Tool to delete a directory at the specified path in backendless file storage. use when you need to remove folders after confirming the path.
Delete File
Tool to delete a file at the specified path in backendless file storage. use after confirming the file's relative path and filename.
Delete Backendless Timer
Tool to delete a backendless timer by name. use when you need to remove a scheduled timer after confirming its name.
Directory Listing
Tool to retrieve a listing of files and directories at a given path. use when browsing or filtering file storage directories.
Connect any two apps with Notis in the middle.
Jira and Backendless, 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 Backendless.