nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

No apps available for tagging to enable HIPAA

Nicolas Mylle

Hi,

I followed this documentation to enable HIPAA on our project, ideally for both JIRA and JSM, but when i reach step 5. I don't see any apps in the popup.

I checked and JSM should be an eligible app, or at least JIRA since we pay for it, but no. Do you have any advice about how to get HIPAA running for JSM ?

Accepted answers

Sami Shaik

@Nicolas Mylle ,

@Matthew Sinclair & @Ismail Bin Ibrahim have the two gates (a signed BAA, and an eligible paid plan with org admin rights). Three things from the docs that would narrow it further before you open the Support ticket:

Check each product's plan separately. Eligibility is Standard, Premium or Enterprise for Jira, Jira Service Management, Confluence and Jira Product Discovery, and "Free and trial plans are not eligible to sign BAAs" (Understand HIPAA compliance for Atlassian apps). A JSM on trial next to a paid Jira would drop JSM from the list. Atlassian Administration, Billing, shows the plan per product.
Service Collection. If the site subscribes to the Service Collection, the same page says you "will need to deactivate the Customer Service Management app" first. That is the one non-compliant app people forget because it arrived as part of a bundle.
Know what tagging does before you tag. Per Tag apps to enable HIPAA, tagging one Jira-family app tags every Jira app on that site together (you cannot tag JSM alone), and afterwards email and push notifications "might be redacted" to keep PHI out of them. Brief your agents on that before it goes live.

Atlassian does not publish the rule for why the dialog shows nothing, so if the plan, the BAA and the apps all check out, the Support ticket is the right next step. Please post back which of the three it was.

All comments

Matthew Sinclair

Based on this: https://support.atlassian.com/organization-administration/docs/the-hipaa-implementation-guide/ I see two potential blockers:

You need to get a signed BAA

You can't have any applications active in the site that are not compliant - so deactivate any apps that are not in that qualified list.

Those two points would likely be what's causing you to not see the applications - beyond that you may need to reach out to support like the document indicated to get assistance → https://www.atlassian.com/company/contact/purchasing-licensing

Also note - Government Cloud isn't supported - nor Free. (Just in case it was missed)

Ismail Bin Ibrahim

Hi @Nicolas Mylle

If the "Tag apps" dialog is empty, I'd first verify that you're using an eligible Jira/JSM subscription and that you're logged in as an Organization Admin. HIPAA tagging is only available for supported products and plans.

If those requirements are met and no apps are displayed, I'd recommend opening a ticket with Atlassian Support, as eligible Jira and JSM instances should appear in the list for tagging.

Could you confirm:

Your Jira/JSM plan (Standard, Premium, or Enterprise)?
Whether you have Organization Admin permissions?
Whether the Jira/JSM site is managed under the same organization where you're enabling HIPAA?

That should help narrow down the cause.

Regards,

Ismail.

Sami Shaik

@Nicolas Mylle ,

Check each product's plan separately. Eligibility is Standard, Premium or Enterprise for Jira, Jira Service Management, Confluence and Jira Product Discovery, and "Free and trial plans are not eligible to sign BAAs" (Understand HIPAA compliance for Atlassian apps). A JSM on trial next to a paid Jira would drop JSM from the list. Atlassian Administration, Billing, shows the plan per product.
Service Collection. If the site subscribes to the Service Collection, the same page says you "will need to deactivate the Customer Service Management app" first. That is the one non-compliant app people forget because it arrived as part of a bundle.
Know what tagging does before you tag. Per Tag apps to enable HIPAA, tagging one Jira-family app tags every Jira app on that site together (you cannot tag JSM alone), and afterwards email and push notifications "might be redacted" to keep PHI out of them. Brief your agents on that before it goes live.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

hipaa

jsm