You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When creating a new issue the "description" field is not always a valid field, but it is always being set. In my case the description field has been removed from the "Task" type and replaced with a custom field, but when running the command jira issue create the description field is always set and this error is printed:
- description: Field 'description' cannot be set. It is not on the appropriate screen, or unknown.
Are you using Jira cloud or on-premise jira server?
SERVER INFO
-----------
Version: 1001.0.0-SNAPSHOT
Build Number: 100278
Deployment Type: Cloud
Default Locale: en_US
What operating system are you using? Also mention version.
macOS Sonoma 14.7.3
What terminal are you using? Also mention version.
iTerm 2 Build 3.5.11
To Reproduce
Steps to reproduce the behavior:
jira create issue --type=Task
On my companies installation, when querying the createmeta for this issue Task, the description field is not present.
Expected behavior
One should be able to create a new jira issue. Either the CLI needs to fetch the createmeta to see that the description field should not be defaulted or another flag needs to be added to disable auto setting this field.
The text was updated successfully, but these errors were encountered:
Describe the bug
When creating a new issue the "description" field is not always a valid field, but it is always being set. In my case the description field has been removed from the "Task" type and replaced with a custom field, but when running the command
jira issue create
the description field is always set and this error is printed:To Reproduce
Steps to reproduce the behavior:
jira create issue --type=Task
On my companies installation, when querying the
createmeta
for this issue Task, the description field is not present.Expected behavior
One should be able to create a new jira issue. Either the CLI needs to fetch the
createmeta
to see that the description field should not be defaulted or another flag needs to be added to disable auto setting this field.The text was updated successfully, but these errors were encountered: