Custom field from add-on does not appear

[Tamas Radocz]

Edit: accidentally posted in the wrong forum, the question is about Jira Server

When I tried to add custom fields, the ones which have a standard type (text, label, etc..) appear correctly, but when I try to add a field which is defined by an add-on, it pops up this notification: "The field was added successfully, but you do not have edit permissions."

It first happened on my live instance, but managed to get the same error on the test instance started by the plugin SDK, both with Jira versions 7.13.0 (the one in the generated plugin POM) and 8.7.1 (edited the POM / the version of my instance)

Steps to reproduce:

1. start up a new Jira instance (atlas-clean and then atlas-run with the linux SDK)
2. login, create example project just to have some example issues
3. Go to Admin / apps and install an addon which comes with custom fields, I installed vLinks (https://marketplace.atlassian.com/apps/1219910/vlinks-easy-issue-linking?hosting=server&tab=support) and MyGroovy (https://marketplace.atlassian.com/apps/1218755/mygroovy?hosting=server&tab=overview)
4. navigate to an issue, click "Admin" / "Add Field", create new text field --> field appears correctly
5. same way, try to create now a field from vLinks --> field does not appear, notification "The field was added successfully, but you do not have edit permissions." is shown.

I could not figure out what that missing permission could be, can anyone help with that?

(Since the exact same problem happened on the SDK test instance, don't think my server context is relevant, but it's the Atlassian Docker image "atlassian/jira-software:jdk8" with Postgres, running on Ubuntu)

[Andreas Ebert]

I have the same problem with vLinks in my customer's Jira after upgrading from Jira 7.13 to 8.5.3 and from vLinks 1.2.9 to 1.3.4. But in my local Jira 8.5.0 it works correctly..

If you have any update, please let me know. Thanks.

[Andreas Ebert]

I found the issue, atleast in vLinks 1.3.4: It cannot handle field contexts where its fieldConfigSchemeId is different than its fieldConfigId. Both IDs are usually identical, but they can be different and on my customer's Jira that is indeed the case. -> Bug in vLinks

Since there is nothing I can do about that directly, I reverted to vLinks 1.2.9 which still works in my customer's Jira 8.5.3. Unfortunately, 1.2.9 is not supported anymore for Jira 8.7.1