Developing new custom-field type using Atlassian Connect.

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

 

2 answers

1 accepted

1 votes

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.

So, if you have developed a custom-field type plugins  with P2 (for standard JIRA standalone server) and your customers ask you to port the code to use your customfield with jira cloud I have to responde that isn't possible? Is it correct?

Yes. P2 code is very different to Connect code - although you can reuse logical stuff like "how I calculate X for display", you'll need to write all the storage, indexing and maintenance from scratch.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,006 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot