atlassian / atlassian/atlascode

[Feature Request] Dynamically fetch Issue Types based on Project Metadata in "Create Issue" dialog

Open
#1,817 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
129
Forks
82
Avg merge
3h 3m
Merged PRs (30d)
6

Description

**Is your feature request related to a problem? Please describe.**
I am frustrated because the "Create Issue" dialog only displays default Jira issue types (Epic, Story, Task, Sub-task) and fails to fetch the actual Issue Type Scheme assigned to the selected project. In my environment, we use custom names and specific task types that differ from the defaults. Currently, I cannot create issues from the IDE for these projects because the required types are missing from the dropdown.

**Describe the solution you'd like**
The "Create Issue" dialog should dynamically populate the "Issue Type" dropdown based on the selected project's metadata.

Upon project selection, the extension should call the /rest/api/2/issue/createmeta endpoint.

The UI should filter and display only the issuetypes returned for that specific projectId or projectKey.

This ensures that custom issue types (e.g., "Research," "Technical Debt," "Maintenance") are available and that invalid defaults are hidden.

**Describe alternatives you've considered**
I have tried manually typing the name, but the dropdown is restricted. The only alternative is leaving the IDE to create issues in the Jira Web UI, which defeats the purpose of the [Atlassian](https://github.com/atlassian/atlascode) extension.

**Additional context**

This is a critical gap for "Company-managed" projects where issue type schemes are strictly enforced. Without this, the creation feature is only compatible with "out-of-the-box" Jira configurations.

Contributor guide

Open the contributing guide

Research direction

Start in the Create Issue dialog and trace the project-selection flow; then inspect how Jira requests are made for the /rest/api/2/issue/createmeta endpoint. Done means the Issue Type dropdown reflects the selected project’s returned types, including custom types, and hides invalid defaults.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.