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

Move card to a new project but keep Sprint

Jason J. Fedelem

I'm currently working on splitting one project into two. This project has been around since 2019 and has a lot of historical data, but the part that is splitting out is pretty small. Somewhere around 1000 cards.

Its mostly going well. However, it keeps dropping the Sprint info when I move it from old project to new project. I've verified that the sprints are available in both projects. So, I can assign it to Sprints that are intended for the new project while its in the old project and vice versa. But as soon as I move the card to the new project, the info drops off the card.

This is going to get really hairy if i can't maintain this info. I don't see a way to do it in Automation either, but maybe I'm not being creative enough.

Thoughts?

Accepted answers

Vasyl Krokha

Hi @Jason J. Fedelem

Sprints are indeed tied to boards, not projects, and projects are tied to boards via the JQL filter that defines a board's scope.

The challenge is cheating and including the old project into JQL without issues. You could try to add a non-existing issue to the old project in the JQL of your new board.

Vasyl

All comments

Benjamin_tmh9yg

Hi @Jason J. Fedelem ,

The issue is the Sprint is tied to the original project. You can possibly use the bulk update feature to make a bulk update to that sprint. That's probably the simplest method to take.

Hope this helps.

Jason J. Fedelem

Thanks for the response!

That was my original thought, but everything I can find on here says that sprints don't belong to projects. Also, I created sprints while in the new project so if they did belong to a project they'd belong to that one.

I then tried to move them to the new sprint that was created while I was in the new project first. That worked, but then when I moved the cards to the new project, they lost the sprint info.

Probably something simple I'm missing.

Vasyl Krokha

Hi @Jason J. Fedelem

Sprints are indeed tied to boards, not projects, and projects are tied to boards via the JQL filter that defines a board's scope.

The challenge is cheating and including the old project into JQL without issues. You could try to add a non-existing issue to the old project in the JQL of your new board.

Vasyl

Jason J. Fedelem

So I solved this in a kludgy way, but it was fast and will work in our situation.

1. Created "short text" field

2. Created an automation rule that says that whenever labels are updated, copy sprint field to the short text field.

3. Bulk added a label to the relevant issues and verified that the info copied

4. Moved all the issues

5. Went back and for the cards in future sprints used JQL search on the short text field and reassigned them.

Not sure I'd recommend this solution but in my case its good enough and lets me move on.

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-cloud