Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

How do I use workflow sharing and custom fields

Svante Gustafsson Björkegren
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 26, 2012

I try to export and import a workflow with the Workflow Sharing plugin but I don't get the plugin to migrate my custom fields.

I have understood that it is only stuff directly tied to the workflow that is included in the export and I wonder how a custom field should be managed.

Do I have to attach the custom field to a screen that is part of the workflow or is there any other way?

Rgrds,

// Svante

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
Svante Gustafsson Björkegren
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2012

Hi Fagner,

Sorry for not having replied earlier to your answer.

No, that was not what I was looking for. I understand how custom fields work in my configuration.

The problem is when I try to export/import a workflow with the Workflow sharing plugin.

Example:

I have created a workflow where I use a newly created custom field, MyField. The only way the workflow knows about this field is if the field has been added to a transition screen in the workflow. If the field MyField only is added to the screens defined in a Screen Scheme for the particular Issue type (which is using the workflow in question) the workflow itself doesn't recognize this, hence it will not include the field MyField into the zip-file created by the plugin. There are three specific screens defined at this level, Create, Edit and View. It is quite common that these are the only screens used.

What I did to circumvent this was to create a "fake" transition in my workflow to which I attached a dummy-screen with all my newly added custom fields. Then the workflow sharing plugin recognized the fields and created them in the JIRA instance I imported it to.

This seems like an un-wanted side effect in the workflow sharing plugin.

Regards,

// Svante

Svante Gustafsson Björkegren
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2012

I missed to point out that the "fake" transition is then deleted from the workflow. But you figured that out I'm sure :-)

1 vote
FagnerF
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 24, 2012

Hi Svante,

If I'm understanding you correctly you want to know how custom fields are integrated with screens.

Actually adding custom fields in the screen is a part of workflow integration (workflow, screens and fields)

So you can add custom fields, and than add it to any screen you want, but you should be careful as you mentioned that you are using a plugin and sometimes it can impact on your workflow behaviour.

Maybe the following documenttation could be better to clarify your doubts:

Configuring a custom Field

Defining a Screen

I hope this helps you.

Kind Regards

TAGS
AUG Leaders

Atlassian Community Events