Developing new custom-field type using Atlassian Connect.

Daniele Piras2

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?

Regards,

Daniele

 

Nic Brough -Adaptavist-

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.