Reference
Permissions, data, licensing
Chatline is an Atlassian Forge app. It runs on Atlassian's platform; the only place it sends data to is the Zoom Team Chat channels you connect.
Jira permissions
| Permission | Why |
|---|---|
read:jira-work | read the changed issue and comment, check JQL filters, read worklogs for the time reminder |
read:jira-user | show who made a change, tell people from apps and automation, show names in the time reminder |
storage:app | keep the settings of the connected channels |
report:personal-data | report the account IDs the time reminder keeps to Atlassian, and forget closed accounts |
Chatline never changes anything in Jira. Only Jira administrators can open its settings.
What goes to Zoom Team Chat
For each change a channel subscribed to: the issue key and summary, the kind of change and who made it, status, priority, assignee and project for new issues, the extra fields you chose, and the comment or description text if those options are on. Digests, sprint and release messages list issue keys, summaries, statuses, assignees and due dates. Time reminders list the names of the people who logged too little and the hours they logged. Jira Automation rules send the text their authors wrote. Everything is sent over HTTPS to integrations.zoom.us, to the webhook of that channel only. Zoom processes posted messages under your organisation's Zoom agreement.
What Chatline stores
- The settings of each channel: name, JQL filter, chosen changes and options.
- The endpoint and the verification token of each channel, in Forge secret (encrypted) storage. They are never shown again or logged.
- Per channel: how many messages were sent and failed, the last error, and the date of the last daily digest and time reminder.
- For the time reminder only: the Atlassian account IDs of the people it checks. They are reported to Atlassian's personal data API every week; closed accounts are removed.
Issue content is not kept. With bundling on, the changes of an issue wait in Forge storage for about a minute (at most five) until they are posted together, then they are deleted. They hold account IDs, never names or email addresses; names are looked up in Jira when the message is posted. While a message waits for a retry it sits in the app's Forge queue for at most about 15 minutes. Logs contain counts only, never issue text, keys or names. When the app is uninstalled, Atlassian deletes its Forge storage according to the Forge data retention policy.
Licensing
Free for up to 10 users, then paid per user through the Atlassian Marketplace, with a free trial. When the license of a site is not active, nothing is posted and the settings are kept. See the privacy policy and the terms.
Contact
Questions or a security report: support@yti.digital. YTI Digital OÜ, Estonia.