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

Apps to move an issue from one project to another

Trudy P Claspill

I am looking for app suggestions for Jira/JSM Cloud for moving an issue from one project to another.

I know that it is not supported by Automation actions yet.

https://jira.atlassian.com/browse/AUTO-549

I'm aware of the "clone & delete" method. It seems like that takes extra work to clone comments and attachments, and I haven't looked at the ability to clone worklogs. Issue history is also lost unless somebody knows of a solution for cloning that too.

I'm looking for a replacement for the Move Issue post function available in Jira Workflow Toolbox (for Data Center) as part of a migration of Jira/JSM to Cloud.

EDIT: Here is the use case -

In workflows a Transition is added specifically to enable moving an issue from one project to another while also changing the issue type. This is being applied to issues moving from JSM projects to other JSM projects, at least. This Post Function is made available by JWT.

https://apps.decadis.net/display/JWTSDC/Move+issue

The solution needs to provide a similar level of automation; i.e. avoid adding more steps that have to be executed by the end user.
Minimizing user retraining is desirable; i.e. if it can be triggered by a workflow transition that would be ideal.
It is preferred that there is no additional loss of data during the move; i.e. the JWT function does move issue history, comments, and attachments.

Accepted answers

Kai Becker

Hi @Trudy P Claspill

I can't really recommend an app to move issues but there is a new REST API to bulk move, which also handles single work items.

I would go ahead and set up an Automation rule with the "Send web request" action

All comments

Kai Becker

Hi @Trudy P Claspill

I can't really recommend an app to move issues but there is a new REST API to bulk move, which also handles single work items.

I would go ahead and set up an Automation rule with the "Send web request" action

John Funk

Yes, I have seen Bill the GOAT Sheboy @Bill Sheboy recommend this several times.

Julia Watson-Clarke

Hey @Trudy P Claspill,

One option you could explore is the 'Import from csv' feature. This will allow you to export work items (issues) from a project into a csv file and then import them into another project / instance.

You'd need to ensure the fields were the same in both projects to ensure the data can be mapped.

You can Export the Work Items (Issues) from a Jira Filter, selecting which data you need to bring over (Export Excel CSV all fields). This method means you essentially have a backup of your data and can retain the data in both instances (you'll need to manage comms around cut-off dates for adding any new Work Items to the current project.

To Import, you'll need to select the 'All work' tab in your project, click the ellipsis and select 'Import work items from CSV':

You'll then need to follow the set up instructions for mapping fields etc.

Hope this helps,

Julia.

Trudy P Claspill

@Kai Becker , thank you for that suggestion. I'll explore that option to see if it will work for the current use case.

@Julia Watson-Clarke , thank you for that suggestion. Unfortunately that is not an adequate replacement for the current use case.

I should've stated the use case up front, and I will edit my post accordingly to add that.

Luka Hummel - codefortynine

Hi @Trudy P Claspill

If you're looking for a convenient way to move issues from one Jira/JSM Cloud project to another, our app Deep Clone for Jira is an excellent solution.

Unlike the manual "clone & delete" approach, Deep Clone allows you to easily clone issues between projects, retaining essential content such as:

Comments
Attachments
Work logs
Issue status
Sprints (active or future)
Custom fields

(It doesn't clone the issue history yet)

Deep Clone also offers post functions that offer the same flexible configuration as cloning via the UI. This includes being able to change the issue type while cloning. The Deep Clone post function should be a drop-in replacement for your workflow.

There shouldn't be any retraining necessary.

For more details, check our documentation on moving Jira issues with Deep Clone.

Trudy P Claspill

Hello @Luka Hummel - codefortynine

Thank you for that suggestion.

I have reviewed the documentation. Can you confirm that I have understood it correctly?

Deep Clone offers a workflow post function that will create the new issue with support for specifying a different project and issue type.

This includes options to clone attachments and Comments and a variety of other fields, but it does not clone the issue History.
Are there native custom field types that are not supported by Deep Clone?

The Deep Clone post function does not delete the original issue. A Jira Automation Rule would have to be created to handle that.

Luka Hummel - codefortynine

Hi @Trudy P Claspill

I think you have understood it perfectly.

There are some custom fields Deep Clone can't clone. We have collected them in our documentation.

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

jira-service-management