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

Customfields are not added to new cards created with the API #4810

Closed
HEMGDevelopment opened this issue Jan 17, 2023 · 4 comments
Closed

Customfields are not added to new cards created with the API #4810

HEMGDevelopment opened this issue Jan 17, 2023 · 4 comments

Comments

@HEMGDevelopment
Copy link

Issue

Customfields are not added to new cards created with the API

Server Setup Information

  • Did you test in newest Wekan?: yes
  • Did you configure root-url correctly so Wekan cards open correctly (see https://github.com/wekan/wekan/wiki/Settings)? yes
  • Operating System:
  • Deployment Method (Snap/Docker/Sandstorm/bundle/source): snap
  • Http frontend if any (Caddy, Nginx, Apache, see config examples from Wekan GitHub wiki first):
  • Node.js Version:
  • MongoDB Version:
  • What webbrowser version are you using (Wekan should work on all modern browsers that support Javascript)?

Problem description

When creating a new card with the API custom fields that are defined on the boards that are set "Add field to new cards" does not show up on cards created with the API.

Reproduction Steps

Create a custom field on a board choose "Add field to all cards" and "Add field to new card".
Create a card on the board with the custom field thru the API.

@xet7
Copy link
Member

xet7 commented Jan 17, 2023

Fixed, will be in upcoming WeKan v6.71.

@HEMGDevelopment
Copy link
Author

@xet7 many, many thanks for fixing this so quick!, and many thanks for a quick release of a new version!

Do you know when the snap will be updated?

Many thanks again!

@xet7
Copy link
Member

xet7 commented Jan 18, 2023

@HEMGDevelopment

There is manual way to upgrade at #4780 , but currently it loses some data like attachment createdAt/modifiedAt/updatedAt . It did work for #4780 (comment) , but not for #4803 (comment) .

For automatic upgrade, it depends when I get more bugfixes done, so it would work in most cases, and also have time to write code to do all those manual steps automatically. Maybe in Q1 2023. Currently I'm writing attachment migrations related code.

@HEMGDevelopment
Copy link
Author

@xet7 thanks for the answer and your dedication to the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants