Skip to content

feat: add support for Team custom field type#927

Open
logan-mcduffie wants to merge 1 commit intoankitpokhrel:mainfrom
TidalStudio:main
Open

feat: add support for Team custom field type#927
logan-mcduffie wants to merge 1 commit intoankitpokhrel:mainfrom
TidalStudio:main

Conversation

@logan-mcduffie
Copy link
Copy Markdown

@logan-mcduffie logan-mcduffie commented Dec 21, 2025

Fixes #637

@logan-mcduffie
feat: add support for Team custom field type
c3fb55d 
The Team field (com.atlassian.teams:rm-teams-custom-field-team) requires
a specific payload format with an "id" property. This change:

- Captures the schema.custom type identifier from Jira's field API
- Adds special handling for Team fields in create and edit operations
- Wraps Team field values as {"id": "uuid"} instead of plain strings

Fixes ankitpokhrel#637
@divansantana
Copy link
Copy Markdown

divansantana commented Apr 15, 2026

I've tried this fork

and this command still fails

jira -c .config/.jira/.config.yml issue create --custom team="myteam"

Additionally I've edited the .config.yml to have nextgen set in the correct place at the project type.

Error:
  - customfield_10362: Field 'customfield_10362' cannot be set. It is not on the appropriate screen, or unknown.
  - customfield_10507: Field 'customfield_10507' cannot be set. It is not on the appropriate screen, or unknown.

jira: Received unexpected response '400 Bad Request'.

@divansantana divansantana mentioned this pull request Apr 15, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Field 'customfield_xxxxx' cannot be set. It is not on the appropriate screen, or unknown.

2 participants

@logan-mcduffie @divansantana