Jira/JSM Cloud Automation - Set work item Data Classification Level

[#1]

I've been spending a lot of time recently learning about the features of Atlassian Guard Premium and explaining them to Atlassian customers.

One customer asked about how they could block the export of work items containing sensitive data in Jira/JSM.

We discussed the use of Data Classification levels ,(Guard Premium) and Data Security policies that block data export based on the Data Classification level of the work item.

They asked how they could automatically evaluate the content of Jira/JSM work items for sensitive data and then set the work item Data Classification level appropriately to block export of that data.

I worked out a solution that uses Guard Detect Content Scanning (Guard Premium) detection rules to scan the content and generate alerts, and combined that with Automation for Jira rules triggered by those alerts to update the work item Data Classification level.

If that is a topic of interest to you, check out the article I published in the Atlassian Automation Articles forum. 

Jira/JSM Cloud Automation - Set work item Data Classification Level

I look forward to seeing your feedback in the comments on that article!

[Bill Sheboy]

Hi @Trudy Claspill 

Thanks for the excellent way you posted this information to refer to the details in your automation article!  It increases visibility to the community while not replicating content.  Well done!

In my opinion, this is the better way to do it...rather than a lot of recent posts (including from Atlassian team members) which post the same exact content in 4-5 places or more.

Kind regards,
Bill