Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Add support for custom fields #301

Open
felickz opened this issue Sep 14, 2023 · 1 comment
Open

Feature Request: Add support for custom fields #301

felickz opened this issue Sep 14, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@felickz
Copy link

felickz commented Sep 14, 2023

customfields themselves are just an additional key/value pair passed to the fields object: https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/#creating-an-issue-using-custom-fields

Ideally the custom field would be an arbitrary map the user passes into the github action. (inspiration for this from here)

Currently a failure will look like:

jira.exceptions.JIRAError: JiraError HTTP 400 url: ...
response text = {“errorMessages”:[],“errors”:{“customfield_#####”:“<field> is required.“}}”
@kasperg
Copy link
Member

kasperg commented Sep 18, 2023

Could you elaborate how you would want to use this?

Our primary approach to configuring the actions is through environment variables. One way would be to add something like a JIRA_CUSTOM_FIELDS variable which could contain a formatted string with key/value pairs for custom fields. The values would be static though.

As far as I can tell the underlying JIRA library that we use also supports custom fields.

@kasperg kasperg added the enhancement New feature or request label Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants