Updating custom field value on moving between projects

I've got custom field type (numeric) field.

Value of this field is id of one of active objects, linked to specific project.

So when i'm moving issue to another project, i wish to update custom field value according to new project.

How this can be done?

1 answer

0 vote


Two options spring to mind - hacking the "move" functionality in the core of JIRA, and not actually doing it in the move at all.

The second option means writing a listener that could catch the "move" event, have a look at the issue and change the number as appropriate (technically, this would happen after the move, not as part of it, but it will usually be fast enough that the users will see it as the same action)

Second is not an option, because there's no way to automatically assign new value.

Basically, i need my field to work just like "fixVersion" do when issue is moved to another project.

It asks for a fix version because fix version lists are different between projects.

You could configure your field so that it has two separate option lists, that would cause similar behaviour.

This is exactly what i need.

Where this confuguration should be done?

It's in the field context stuff.  Custom fields -> find your field -> configure

You should find a screen that says "this field belongs to some projects and has the following options", along with the ability to edit the options.

Towards the top of that, you'll find an "add context" button, use that and choose which project(s) or issue type(s) to apply it to.  Then define the new list.

Note - this may be destructive, I can't remember how it works!

Thing is, that value of my custom field is actually ID of active object, which is created/updated/deleted through custom editor in project administration interface.. 

I've examined JIRA MoveIssueUpdateFields class and found that there's hasValue() method of OrderableField object, which determines if the field has a value for the given issue. Fix version uses that.

Bad news is that custom fields created through "customfield-type" plugin module doesn't inherit OrderableField.

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,311 views 14 20
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