How to add jira:customFieldType with UI Kit?

Forge Forge UI Kit and Custom UI
, ,
1

Hello there,

I am trying to add a jira:customFieldType with UI Kit. Documents are confusing as always unfortunately. In the module description Object data type is listed as a valid type:

image
image1570×1174 171 KB

However, in the example, jira:customField is used. How can I add a custom field type with object data type?

image
image1718×1610 310 KB

In the same page there are also some indicators that Object
When I try to use it, it gives me the following error:
jira:customFieldType property type 'object' allowed values are 'date', 'datetime', 'group', 'number', 'string', 'user'

According to the example here this must be correct:

modules:
  jira:customFieldType:
    - key: aip-assets-field-type
      render: native
      name: Forge Assets Type
      description: A custom field with forge
      type: string
      formatter:
        expression: "This string is used to represent the value if the rendering function is not provided, or where the rendering function is not supported."
      readOnly: false
      resource: cf-view
      resolver:
        function: cf-resolver
  function:
    - key: cf-resolver
      handler: ?
resources:
  - key: cf-view
    path: src/frontend/custom-field-type/index.jsx

However, I couldn’t figure it out how to handle function with this example? Where is handler here?

image
image1568×680 49.9 KB

Kind regards,

2

I’m having the same issue while trying to upgrade to the new UI Kit. Did you ever figure out how to resolve?

3

Hi @AshAsh ,

Here is my manifest file:

Module definition:

modules:
  jira:customFieldType:
    - key: aip-forge-asset
      name: Forge Assets CFT UI Kit
      description: Experimental
      type: object
      formatter:
        expression: "Placeholder"
      schema:
        properties:
          assetIds:
            type: array
            searchAlias: assetIds
            items:
              type: number
      readOnly: false
      render: native
      resource: cft-main
      resolver:
        endpoint: connect-endpoint
      edit:
        render: native
        resource: cft-edit
      contextConfig:
        render: native
        resource: cft-configure

As you know render: native means the UI Kit.

Resource definition:

resources:
  - key: cft-main
    path: src/frontend/cft/index.jsx
  - key: cft-edit
    path: src/frontend/cft/edit/index.jsx
  - key: cft-configure
    path: src/frontend/cft/configure/index.jsx

I hope this helps :slight_smile:

I will be happy to answer if you need more questions.

Kind regards,
Furkan