Known limitations

Owned by Peter Atthem
Last updated: 2024-09-17
2 min read

Due to the Atlassian cloud integration limitations there are some parts where we yet can not plugin to. As soon as these are available to plugin to and extend the function then Rixter is committed to implement these features. These are marked as Waiting for atlassian platform support in the text below.

  1. Waiting for atlassian platform support Team based projects (NextGen) is not supported. This is due to that there is no way at the moment to hook into those projects

  2. Old Issue View is not supported, due to that there is no hook at the moment. Use the new view to use the tool (https://support.atlassian.com/jira-service-management-cloud/docs/changes-to-requests-in-the-new-issue-view/)

  3. Setting an invalid value as Default value on a Protected field that has Global context may prohibit issue creation for all projects not having the field on its create screen.

    1. Make sure to to use Context to limit the field to the projects using it.

    2. Make sure to use the correct format on the input value if using default value, specified here Protected Field Types

  4. Waiting for atlassian platform support Agile Card - Field value shows encrypted value on card. (Works with unencrypted fields)

    first line show unencrypted value, sencond line shows encrypted field



  5. Waiting for atlassian platform support Export to CSV or Excel - when exporting as CVS or Excel the encrypted values comes out as encrypted strings.

  6. Waiting for atlassian platform support Importing values into encrypted field is not yet supported, use the API as workaround. Importing into unencrypted is supported for type text.

  7. Waiting for atlassian platform support Filter / Search view - Encrypted values will be displayed as an “View is not supported“, hence not searchable yet.

  8. Can Protected Fields secure other vendors fields? No, the nature of the Atlassian cloud prohibits apps to interfere or override behaviors of other apps and core functionality. Only known extension points from app vendors can we used, these are very limited today. Each app also renders as a iFrame inside Atlassian cloud which makes them isolated.

  9. Protected Fields is hidden on a Request Type on the Customer Portal in Jira Service Management - Today Atlassian Forge framework does not allow vendors to show fields on the customer portal yet

  10. Forms (new) feature is not yet supported.

  11. “Log in as” in the administration of Atlassian it is possible to login as another user if you are an admin. Protected field can not recognize the “Logged in as user” when running the session. The result will be that it treats the session as the current user instead and all permission will be based on that.

  12. Bulk Edit values does not show in select boxes until a issue has one of the values, When trying to perform bulk edit on issues that does not yet have any PF values then the bulk edit shows a blank drop-down. As soon as one issue has a PF value the dropdown will be populated and bulk edit will work.

  13. Transition screen does not work, all values shows you have not permission to view this value.
    WORKROUND Transition screen workaroundwill describe how to use transition screens.