nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I move issues with custom, multi-select fields

Anthony Newnam

I have a multi-select field in project A, and I would like to bulk move issues into project B, which has the same named field with the same named values. When I do a bulk move, everything else is found correctly except this field, which it asks me for a value for.

How can I move these issues and retain the value? This seems like the bug I found at https://jira.atlassian.com/browse/JRA-4551; perhaps this has resurfaced?

Accepted answers

All comments

Dieter

Do you have two fields with same name in your system? That might not work if the field in the source project is not known in the field configuration context of the destination. You should check this first. But i have no idea why it should not work if there is one field with a configurstion context which contains source and destination project

Anthony Newnam

I'm not clear what you mean by "known in the field configuration context." I have a multi-select that is named identically ("Product/Cusomer") and it has several options to select.

Dieter

Ok, so if you look at your custom fields in administration mode you see two fields, both named "Product/Customer", right?

Dieter

I'm asking this because two field with the same name are actually different fields for Jira and bulk move cannot move values between different fields

Anthony Newnam

Yes, they have the same name, but they have different field identifiers in JIRA.

Ramiro P

It may not be correct, but I have understood that you can use the same field in different proyects. I think that if you use the same field you won't have any trouble.

Dieter

you can't move field values from a custom field to another custom field (one with another id). You should use one custom field and have a field configuration context on this custom field that contains both projects (source and destination). Or just make the custom fiel global