Looking to Obfucate a custom field

[Robert Nadon]

Hi all,

For custom fields such as credit card and social security number, it would be nice to be able to obfucate part of the  field (say everything but the last 4 digits) and I was wondering if anyone know how to do that.

The only way I thought of was to use automation to populate a new field with xxx-xx-1234 for example and have the new field on the view screen and the other field on the edit and create screens.  

Anyone know of any other methods?

Thanks,

Robert

[Mark Segall]

HI @Robert Nadon 

Natively, there's no way to really lock down that information.  Yes, you can go with the approach you mentioned.  However, anyone with browse projects permission can create a filter and add the original field as a column in the results. 

I would ask why this information is being captured in Jira?  Typically, sensitive information should only be captured long enough to process and then clear it out.  For example, if it's captured to perform some onboarding activity, it is cleaner to have automation send the data to the appropriate system of record and then delete the data once it gets the successful response.

If this is an important aspect of your Jira implementation, you should probably explore the Marketplace for apps that can provide another layer of protection.

[Nic Brough -Adaptavist-]

The only way I've seen to do this securely is with dedicated code for a custom field of a type that displays and reports its contents obfuscated.  You can't do it natively without either data loss (the xxxx part of your data really does become xxxx) or without letting people have access to the non-obfuscated data in , as @Mark Segall says

I have to admit I wrote this for Jira 3, but I've not seen anything in the marketplace that can do it now.

[Robert Nadon]

Thanks Nic and Mark,  Yeah I just was asked by a customer and couldn't find an apps from my marketplace searches to do it.  So this led me to be curious if there were anything out there.   

Mark, I agree and do not have a real use case was just asked by an Atlassian customer (I am a partner architect).