How to Dynamically Load Issue Types in a Forge App

[Vitheya Monikha]

Hi,

I'm currently working on a Forge app, and I've successfully implemented functionality to dynamically load all custom fields via the REST API during project configuration or creation. However, I’m facing a challenge with the issue types.

Let me explain the use case:
Whenever a new project is created using the app, I want to automatically load (or associate) the relevant issue types dynamically, without having to manually add them later. For instance, if I have a custom issue type like “Testcases”, I currently need to manually create or associate it with the project after setup, which isn't ideal for automation or scalability.

Is there a recommended way or API endpoint in Forge or Jira Cloud that allows us to dynamically load or associate issue types to a project during the Forge app runtime?

Any insights or suggestions on how to automate this step would be greatly appreciated.

Thanks in advance!

[Vitalii Rybka]

Hi @Vitheya Monikha, great question, ran into something similar recently.

Unfortunately, as of now, Forge doesn’t directly expose permissions to associate issue types with projects dynamically during runtime (especially during project creation) this is typically managed via issue type schemes, which must be configured at the global Jira level and associated with the project post-creation.

Here’s a possible approach that may help automate your flow:

1. Predefine an Issue Type Scheme that includes your custom issue type (e.g. “Testcases”).

2. After the project is created, use the Jira REST API (v3) to associate the issue type scheme to the project:

   PUT /rest/api/3/issuetypescheme/project { "issueTypeSchemeId": "10001", "projectIds": ["10010"] }

   This call requires admin-level permissions and must be made from a backend resolver with the appropriate scopes.

3. If your Forge app creates the project itself (via Connect or external app integration), you could follow up immediately with this association logic.

⚠️ Just keep in mind: Forge apps run in a sandbox and currently can’t create issue types or schemes so you’ll need to predefine those manually or manage them externally (e.g. via automation scripts outside Forge).

Let me know if you want help setting that up or writing the resolver code feel free to DM