Error when defining custom field 'experience' property

Forge Forge Modules and Product Triggers
1

I’m trying to use the new manifest shape for Forge Custom Field Type. It introduces an ‘experience’ property. What am I getting wrong?

  jira:customFieldType:
    - key: my-cf-type
      name: My custom field type
      description: A custom field type that is mine
      type: object
      view:
        resource: field-view
        render: native
        experience:
          - 'issue-view'
        ...

Forge lint produces these errors:

523:2 error jira:customFieldType view property experience must be string valid-document-required

523:2 error jira:customFieldType view property experience must be equal to constant valid-document-required

523:2 error jira:customFieldType required properties are ‘description, name, type, key’ or ‘description, name, type, view, key’ or ‘description, formatter, name, type, key’ valid-document-required

527:6 error jira:customFieldType property type ‘object’ allowed values are ‘number’, ‘string’, ‘user’, ‘group’, ‘date’, ‘datetime’ valid-document-required

X 4 issues (4 errors, 0 warnings)
Issues found are not automatically fixable with forge lint.

Line 523 is the one with the jira:customFieldType tag.
I’m running Forge CLI version 11.3.0

2

Hi @david.pinn

Could you please provide the complete code snippet for customFieldType? Having access to the full code will enable us to more accurately identify the root cause of the issue.

Thank you in advance for your assistance.

Best regards,
Szymon Rekawek

3

Private message sent.

4

Thank you for providing the code snippet @david.pinn.

We’ve identified the problem, which is an issue on our end related to the experience in customFieldType. We have begun working on a fix and expect it to be available shortly.

We’re really grateful for your help in identifying the issue.

Best regards,
Szymon Rekawek

1 Like
5

Hi @david.pinn

I’m pleased to inform you that the issue has been resolved. We are now awaiting the release of the new CLI version.

In the meantime, you have the option to test the fix through our Early Access Program. You can do this by downloading the next CLI version using the command:
npm install -g @forge/cli@next

Thank you for your patience and support.

Best regards,
Szymon Rekawek

6

Success! It survives lint and deploys. Thanks, Szymon.