Getting UI Kit 1 deprecation warning for JQL Function and Workflow Validator modules

Hi all

I’m using the Forge CLI version 10.9.2.

I noticed after upgrading to that version today that the deploy command now includes a warning if your app contains any UI Kit 1 components.

My understanding is that UI Kit 1 apps are limited to apps with UI elements? I ask because It’s complaining that my JQL Function and my Workflow validator are recognized as UI Kit 1 apps even though they don’t have any @forge/ui components.

See below for sample output when I created a new demo JQL Function

Start with a template. Each template contains the required files to be a valid app.

? Select a category: Show All
? Select a template: jira-jql-function

 √ Creating app...

i Downloading template
i Registering app
‼ Warning: Your app is currently using deprecated UI Kit 1 modules: issuesWithText-function. UI Kit 1 will be removed on February 28, 2025. Please refer to the documentation (​https://developer.atlassian.com/platform/forge/ui-kit/upgrade-to-ui-kit-latest/#upgrade-from-ui-kit-1-to-ui-kit-latest-version​) to upgrade your modules.
i Creating environments
i Installing dependencies

√ Created demo-jql-function

Your app is ready to work on, deploy, and install. We created 3 environments you can deploy to: production, staging, development.

To dbl check, I created demo apps of the current implementation of a JQL Validator and Workflow validator and out the box, the CLI also flags those 2 as UI Kit 1 apps.

Is the CLI misidentifying those apps? I don’t see any mentions of impacts to those components in the Forge documentation. Those apps also don’t appear under the UI Kit templates lists (or even the old UI Kit module documentations, from what I could see).

See the manifests below of the out-of-the-box validator and jql function.

modules:
  jira:jqlFunction:
    - key: demo-jql-function-issueswithtext-function
      name: demo-jql-function
      arguments:
        - name: text
          required: true
      types:
        - issue
      operators:
        - in
        - not in
      function: functionKey
  function:
    - key: functionKey
      handler: index.issuesWithText
app:
  runtime:
    name: nodejs22.x
  id: ari:cloud:ecosystem::app/e743c533-4276-4be4-9496-a67a3b86fba2
modules:
  jira:workflowValidator:
    - key: demo-workflow-validator-example-workflow-validator
      function: main
      name: demo-workflow-validator
      description: A Jira workflow validator example.
  function:
    - key: main
      handler: index.run
app:
  runtime:
    name: nodejs22.x
  id: ari:cloud:ecosystem::app/8cd0fbe7-8d56-47fd-8910-f12ae183a299

If these are indeed considered UI Kit 1 apps, Atlassian needs to update their documentation to give clearer guidance since just looking for apps that use @forge/ui is not enough. Atlassian also then needs to update their templates to be compliant with the deprecation

We’re a month away from it.

@DeonPetrusMeyer Please ignore that warning :pray:, your understanding is correct. We are working on the fix for the filtering right now.

Apologies,
Yuwei

1 Like

@DeonPetrusMeyer The warning should no longer appear in the new @forge/cli@10.13.4 for jira:workflowValidator and jira:jqlFunction.

3 Likes