Transfer Items Between Projects #10826
Replies: 14 comments 6 replies
-
|
Since issues can have multiple projects, you can open the issue, click the gear icon next to Projects and click on the project needed. |
Beta Was this translation helpful? Give feedback.
-
|
This would be a very helpful feature, as moving draft pull requests around our project boards would help streamline our planning process. Has there been any movement on this question? |
Beta Was this translation helpful? Give feedback.
-
|
May I ask if there is any progress made to this item? I need to move items from backlog project to a working project, I have to use remove/add approach, which is very inefficient. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Yes, suffering with this now. Have accidentally been using a template to store all my items for a long while. If I click 'use as template' it loses all the items. So I thought copying the items instead would be the way, but I can't. If i load from the issues I lose all the additional information in the project table. For now I will still have to use it as a template project and make the situation worse until I can more the items out of the template project. |
Beta Was this translation helpful? Give feedback.
-
|
Dealing with this now, as I'm moving all of our issues from a 2023 project to a new 2024 one. When I put the issue into the new project, I lose all of the custom fields assigned and it's a nightmare having to manually reassign everything. |
Beta Was this translation helpful? Give feedback.
-
|
Same here, moving items between projects would be big help!! |
Beta Was this translation helpful? Give feedback.
-
|
Definitely need this feature! Currently we have to copy paste each ticket item between project boards, and that's a PITA. |
Beta Was this translation helpful? Give feedback.
-
|
My team would definitely make use of this feature - it's much needed! |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
I need this feature please. In the real world we'd walk a card or post it from one board to another. whether that card is an issue, item, task or whatever it needs to move and not hang around getting in the way. Having it (some kind of job card) exist in two places at once would be a recipe for human error. The issue in multiple repos being a case in point. |
Beta Was this translation helpful? Give feedback.
-
|
We would need this too. |
Beta Was this translation helpful? Give feedback.
-
|
You can easily add tasks to a new project. Steps:
Nuance: the tasks will be in two projects. If the goal is to delete the old one, then after these actions the old project is simply deleted. If the goal is to move some tasks, then these tasks will need to manually disable the project through the menu in the task itself. The main problem with this approach is that the task list itself will not “disappear”, since they will be in two projects after the changes. But this can be easily fixed by applying an exclusion filter. For example, we have two projects - “foo” and “bar”. We need to move tasks from the “foo” project to the “bar” project and then delete the “foo” project. Open the Issues page and select the filter for the “foo” project. In the filter field we will see something like The goal: to quickly get the project identifiers. For example, it will be Now we need to enter a condition in the filter field: And press “Enter” After that only those tasks will be displayed in the list, which are in the “foo” project and which are not in the “bar” project. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I didn't have the time to learn their GraphQL and figure out how to preserve all the fields. But here's a simple solution to move between projects using gh cli. OWNER=example
SRC_PROJ_NUM=1
DST_PROJ_NUM=2
main() {
SRC_ITEMS=$(get_proj_items "$SRC_PROJ_NUM")
# jq . <<<"$SRC_ITEMS"
local src_title=$(get_proj_title "$SRC_PROJ_NUM")
local dst_title=$(get_proj_title "$DST_PROJ_NUM")
local item_id url title item_json
while read -r item_id url title
do echo "Moving item $item_id ($title)..."
item_json=$(get_item_json "$item_id")
# jq . <<<"$item_json"
gh issue edit "$url" --add-project="$dst_title" --add-label="$src_title"
# TODO: also copy fields (using graphql?)
# once we've safely copied over all metadata/fields...
gh issue edit "$url" --remove-project="$src_title"
echo "Item $item_id moved."
done < <(get_items)
}
get_proj_items() {
gh project item-list "$1" --owner="$OWNER" --format=json
}
get_proj_title() {
gh project view "$1" --owner="$OWNER" --format=json --jq=.title
}
get_items() {
jq --raw-output '
.items[] |"\(.id) \(.content.url) \(.title)"
' <<<"$SRC_ITEMS"
}
get_item_json() {
jq ".items[] |select(.id==\"$1\")" <<<"$SRC_ITEMS"
}It cheats and adds a label on the issue with the name of the old project. You must have already created that label in the repo. |
Beta Was this translation helpful? Give feedback.





Uh oh!
There was an error while loading. Please reload this page.
-
It would be great if we could transfer an item between projects.
Down by the "convert to issue" option there would be another option that says "Transfer to Another Project." When clicked, a similar UX to that of the issue creation would show, allowing the user to pick a project to transfer the item to.
Beta Was this translation helpful? Give feedback.
All reactions