Jira + Data Alias: File the protected result as a new Jira issue
Why use Jira with Data Alias
Findings from an analysis often turn into work to track. Filing them as an issue keeps the aliases in place and real names out of the tracker.
How it works
Jira uses the same Atlassian app, sign-in and site choice as Confluence. You pick a project and an issue type, and the issue is created from your browser straight to Atlassian. The description is built from plain text only, so nothing in a cell becomes formatting or a mention. Each issue carries a label unique to that save, which is how Data Alias finds an earlier issue if an answer is lost.
What it does
- Create a new issue in a project and issue type you pick
- Write the description as plain text — no mentions or links are produced
- Tag the issue with a label unique to the save
- Refuse to send a save whose label couldn't be searched for later
How it will connect
These are the steps once the connection is available. Until then: Download the safe copy from Data Alias and attach it to a Jira issue yourself.
- 1
Connect
The same Atlassian connection as Confluence, with three Jira permissions: read projects, read issues and write issues.
- 2
Pick a site, project and issue type
Only sites your account granted are listed.
- 3
Review in your browser
Detection, your rules and the review before export run in the tab, the same as for an uploaded file. Change any suggestion you disagree with.
- 4
File the issue
A new issue is created. Existing issues are never edited.
What moves where
- What reaches Data Alias servers
- Only the one-time sign-in code. The issue goes from your browser to Atlassian.
- What is written to Jira
- A new issue with a dataalias- label.
- Never sent
- The original file, the alias mapping, and restored results with real names never leave your browser.
- Who holds the access token
- Your browser tab, in memory only, for about an hour. No refresh token exists.
Limits worth knowing
- Finding an earlier issue relies on Jira keeping the label exactly as sent and its search finding it.
- Without offline access you reconnect more often.
Can I connect Jira today?
No. The connection is built and tested against stand-ins for Jira, but it hasn't been run against a real Jira account, so there is nothing to connect yet. Download the safe copy from Data Alias and attach it to a Jira issue yourself.
Can it edit an existing issue?
No. The only write in the code creates an issue, and it carries no issue id.
What is the dataalias- label on the issue?
It identifies that one save. If an answer is lost, Data Alias searches for the label before doing anything, so it reports the issue that exists instead of filing another.
Data Alias reduces exposure risk but cannot guarantee detection of every sensitive value. Every transfer passes the same review as a download — check the result before you send it. How connected services are handled.