Hi,
I encountered an issue while using the `acli jira workitem create` command.
## Problem
The command fails with an "invalid issue type" error, even though the issue type is listed as allowed.
## Example
Command:
acli jira workitem create \
--project "SECP" \
--parent "SECP-3387" \
--type "Sub-task" \
--summary "[TEST] Sub-task creation test" \
--description "test" \
--assignee "@me" \
--json
Error:
The selected issue type is invalid.
## Observations
- The issue type appears in the allowed issue types list
- The same operation works correctly via Jira REST API
- In some cases, even using a numeric issue type ID does not resolve the problem
## Important Detail
Although there are multiple issue types with the same name in the global Jira configuration,
only **one issue type with that name is actually associated with this project**.
In other words, from the project’s perspective, there is no ambiguity.
## Suspected Cause
It seems ACLI may be resolving the issue type at a **global scope** rather than within the **project scope**.
When multiple issue types share the same name globally, this could lead to incorrect resolution,
even though the project itself has only one valid match.
## Additional Notes
- This situation can occur when:
- Team-managed (next-gen) projects are created or deleted
- Issue types are duplicated across different scopes
- Jira is known to allow duplicate issue type names with different internal IDs
## Suggestion
- Resolve issue types strictly within the project scope
- Or prioritize ID-based resolution over name-based matching
- Provide a clearer error message when ambiguity is detected
## Question
Is this a known limitation of ACLI, or is this considered a bug?
Thanks.
