I saw that a similar question has already been done but the response don't convince me.
I need to develop this type of plugin for atlassian connect and extends the issue page and use the entity properties to store information IMHO isn't a correct way.
All the feature of developing customfield with P2 are missed: configure one or morecustomfields/screens/project where do you want the customfield and so on.
So If I want to create a custom-field with atlassian connect I have to write all code to manage all this missing features.
What is the correct way? Extends issue page and write all code to manage your customfield visibility/numbers/and so on is really the correct way?
There is a demo code to develop new customfield type with Connect?
Right, well, the short answer is "you can't".
Custom fields hook deeply into the internals of JIRA and are supported by the plugin framework around them. When you create a custom field addon, JIRA handles a lot of the backend for you - storage, indexing, screen locations etc etc etc. Connect is more abstracted and simply doesn't have that level of access to the internals.
So while you could replicate some of the functionality of a custom field with Connect, yes, you'd have to write all the rest of the structures for maintaining it, but also storage, and a separate way of indexing and searching it.
The last time I remember this being asked, I think @Travis Smith said something like "A custom field type" doesn't work in Connect as it does in a P2 addon. Everything in Connect is more or less a bolted-on instead of integrated.
With Connect, you do need to handle all the storage, UI, and searching. You can store the data as an entity property and I'm guessing we'll see indexable entity properties one day because we now have indexable content properties in Confluence. If you store it in your add-on, you'll be 100% responsible for searching, indexing, and storage of that data.
Another URL explaining the workings of an issue field module, based on the example demo:
You need to add field options for this field via REST api call first:
There is also an UPDATE api call to update those field options after ie. updating data so that the fieldoptions get updated with latest source information.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events