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; } } }

Work Item Migration pulls in Work Items from a Space that is not in the Filter

Albert Chirighin

HI All,

I'm working on migrating all work items from Space A to Space B using the Jira Bulk Change Work Items tool. When I get to step 3 of 4 (Step 3 of 4: Select destination projects and issue types), Work Items from Space C are included in the Migration Mapping.

Any ideas why this is and how to avoid migrating Work Items from Space C?

Note, the Filter I'm using is Select All Work Items from Space A.

Thank You!

Accepted answers

Trudy P Claspill

Hello @Albert Chirighin

Can you show screen images for each step you are executing? Obscure confidential information.

All comments

Nikola Perisic

Hello @Albert Chirighin

The space that you are migrating too, the filter that is showing work items on the board, does it contain space C as well?

Marc -Devoteam-

Hi @Albert Chirighin

Can you outline your steps including screenshots.

It must be related to the filter, as issues linked to the moved issues will not move.

Trudy P Claspill

Hello @Albert Chirighin

Can you show screen images for each step you are executing? Obscure confidential information.

Albert Chirighin

Hi All,

@Nikola Perisic , I'll check the board. In the meantime, below are screenshots of the filter I'm using. I even tried to explicitly exclude Space C. I could only check the work item in Space B, but that would take hours as there are ~2000 work items. I'm filtering by Creator to reduce the number of results to below the 1000 limit. I could also migrate from Space C to Space C in Step 3, but that seems clunky. Note, I am playing in my Sandbox.

Thanks All

Trudy P Claspill

Hello @Albert Chirighin

The reason for the additional issues in the results is the use of the OR operator in your filter. All the criteria connected by AND are getting grouped together as one selection, and then it is looking for issues that match either of the OR criteria.

I think you intention is to get Tasks from project A where the creator is any one of 3 people. If that is the case then this is the correct syntax.

project=A and issuetype= Task and Creator in (user1, user2, user3)

If I have not understood your intention correctly, please explain what your intention is for this filter.

Additionally, I see that you have a "(" at the beginning of the filter but I don't see where the matching ")" is placed. Can you show that?

Albert Chirighin

Hi Trudy,

Thank You! Rather than rework the existing query, I created a new one and it only pulled in work items from the source Space I needed it to. I was able then to reduce the number of records in the result by using the Creator field. This allowed me to chunk the bulk process and migrate all of the work items.

Thank You again for the suggestion, and have a great day,

Albert

Marc -Devoteam-

Hi @Albert Chirighin

The problem is your filter based on the JQL clauses;

based on the "or creator = " options.

These clauses, look at each issue created by user A, B and C

Your JQL is no getting all issues from project BI2 and all issues created by user A, B and C.

If you want to move issues from project BI2 why are the users added in the JQL.

If you want only the items from project BI2, created by users A, B and C?

JQL: project = Bi2 and issuetype = task and creator in ("user A", "user B", "user C")

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-cloud