Hi @Aleks , welcome to the Atlassian Developer Community!
This does not mean that you are forced to do it with Custom UI. Just to clarify, only the CustomFieldEdit modal will be deprecated as mentioned in the changelog. This means you can still use the existing UI kit implementation (with the assumption that you already have one), bump the @forge/ui version to 1.2.0, and then redeploy the app.
If you are a more visual person, here are some screenshots to hopefully clarify the change.
Prior to the change Notice that it is shown as a modal
Can you double check if your project’s package-lock.json has been updated? Assuming you updated package.json, try running npm install so that package-lock.json will be updated and reference the latest @forge/ui version. Do another forge deploy after npm install.
That looks correct. I tested playing around the versions of @forge/ui and every time I am getting the expected behavior - I cannot replicate what you are experiencing. I’m wondering why the changes aren’t being reflected on your instance after doing a forge deploy
Here are some thoughts:
Do you have a custom field with the same key installed on the instance? If so, try removing the possible conflict.
Have you tested on a different instance and see if you are getting the expected behavior.
Try uninstalling the app via forge uninstall < installationId> then install again via forge install. You can get the installationId when calling forge install list.
If none of these work, even installing on a different instance, kindly raise the ticket in Developer Support Service Desk so that we can investigate further.
Thanks for the clarification, @aleks and @WolfgangLandes. Apparently, I missed the part where it mentioned customFieldType in the original post, my apologies. I am now able to replicate the issue by using the Forge Currency Exchange example app (for the jira:customFieldType).
I’ll run some more tests, reach out to the team regarding this behavior, and get back to you.
Hello, @Aleks and @WolfgangLandes. I heard back from the team working on this and the team made a developer community announcement. This confirms the current behavior wherein the change only applies to jira:customField but will be available in jira:customFieldType in the next couple of weeks.
Again, thank you for your patience, and I hope this helped clarify the original question.