General App Documentation
General App Documentation
Breadcrumbs

Limitations of Confidential Fields

Limitations due to missing integrations

Various Atlassian cloud integration issues limit the Confidential Fields app’s functionality. We are very eager to implement the missing features as soon as Atlassian allows it.

Please feel free to vote for and watch the tickets that are linked below.

Issue Description

Atlassian Ticket/Communication

You can add Confidential Fields to screens at any stage by following this instruction. However, Confidential Fields data can only be displayed in the Issue View.

https://ecosystem.atlassian.net/browse/FRGE-135

https://community.developer.atlassian.com/t/support-for-forge-custom-fields-on-transition-screens/56018

Confidential Fields are not displayed on a Request Type on the Customer Portal in Jira Service Management. Currently, the Atlassian Forge framework does not allow vendors to show fields on the customer portal.

https://ecosystem.atlassian.net/browse/FRGE-778

https://ecosystem.atlassian.net/browse/FRGE-320

Resolved limitations

https://communardo.atlassian.net/wiki/s/626371833/6452/634cf7c37efa7b4eab54b193b5c882fc93d0b2af/_/images/icons/emoticons/check.png As of Spring 2023, Confidential Fields can be used both in company- and team-managed projects. Before, it was only possible to use them in company-managed projects.
See https://community.atlassian.com/t5/Jira-Cloud-Admins-articles/Announcing-the-ability-to-re-use-global-custom-fields-in-team/ba-p/2209113


Limitations due to the nature of Confidential Fields

  • Since the data in the Confidential Field is encrypted, the Jira search cannot be used to search for the entered information.

  • For the same reason, Confidential Field data cannot be accessed via the API.