HTMLdb Developer
Tasks
Your Jira work, cached in the database and edited in place. Tasks keeps a copy of your Jira issues in the database, so lists open instantly and filter as you type. Every change you make goes straight back to Jira.
Every feature of Tasks, and how its security works.
Your lists
- My tasks, On hold and Unassigned, each with its own filters
- Status, project, type, priority, assignee, creator and labels
- You first in every people list
- Cards on a phone, a table on a desk
A task
- Move through the workflow Jira allows
- Assignee, priority, due date, labels and description
- Comments with @mentions, work log, every field
- Attachments: upload, preview, download
- Linked work items in a table, add or remove links
Many tasks at once
- Select some or all, change status, assignee or priority together
- Activity: everything that changed, newest first
Always current
- A scheduler job syncs the cache
- A countdown to the next sync, and Sync now
Security
Signed in with App Builder
Every page and every request checks the APEX session and that the browser is signed in to App Builder as a developer of the workspace. Nothing runs before that check.
Nothing trusted from the browser
Requests are POSTs to the package that owns them. The user and workspace come from the checked session; names, paths and keys are validated before they reach SQL or a URL.
Secrets stay on the server
API keys, OAuth tokens and certificates are stored AES-256 encrypted with a fresh IV for every value. The browser only ever learns whether a secret is set.
