"No matching validator for module type jira:command" Error When Using jira:command

Forge Forge UI Kit and Custom UI
,
1

Hi everyone,

I’m developing a Forge app for Jira and trying to use the jira:command module. However, as soon as I call invoke(), I get the following error:

image
image1976×606 181 KB

My Manifest File:

modules:
  jira:command:
    - key: test-command
      title: Test Dialog
      shortcut: i r
      target:
        resource: customui
        render: modal  # Using Custom UI, so I set it to modal.
      icon: arrow-right
      keywords:
        - test

resources:
  - key: customui
    path: customui/build
    tunnel:
      port: 3000

Things I’ve Tried:

:white_check_mark: Checked if my CLI is up to date with forge --version.
:white_check_mark: Ran forge lint to validate the manifest (no errors).
:white_check_mark: Deployed with forge deploy and reinstalled with forge install --upgrade.
:white_check_mark: Ensured that the function I’m invoking is defined in the manifest.

Is there something I’m missing? Does jira:command require any additional configuration?

Thanks in advance!

5 Likes
RFC-67 Forge Command Palette
RFC-67 Forge Command Palette
2

Where did you get that from? I think this line is incorrect and can be deleted.

3

Hello @AndreasZink

I copied this entity from https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-command-palette/#manifest-example this link. You can check it.

4

Ok, but it does not say to use a value of “modal” if using Custom UI. Simply try to delete that line.

You usually set “render: native” when using UI Kit, like in your linked example. When using a Custom UI, you can delete the “render” attribute. But your resource should point to the build output directory of your Custom UI, of course. This already looks correct.

2 Likes
5

Thank you for attention @AndreasZink . You are right. I will fix it. But my error about invocation. Please let me know if you can fix

6

Hi all,
Currently there is no way to overcome this issue with resolver from the app side, will post update as soon as it’s fixed

7

Thank you @PavloBohdanRavliv . We are waiting :rocket:

8

Hi all,
resolvers should be usable now, can we verify that problem is solved?

9

@PavloBohdanRavliv Thanks for update. It works now :rocket: