[bug]: Unable to transfer or update a task to another project

[melgo-tb]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current behavior

While trying to change the project by clicking on the project and selecting another project it moves back to the same project. Unable to move tasks across projects

Steps to reproduce

1. Create a task in a project
2. Edit Task
3. Try changing task of the project
4. Frontend re-renders back to original project after selecting another project

Browser

Google Chrome

Version

Cloud

[vihar]

Currently, our platform doesn't support the transfer of issues from one project to another, @melgo-tb. The only way to have a relationship between issues in different project is via Blocks and Blocked by attributes. Good news, though, transferring issues is already in dev.

Curious. When do you move issues from one project to another today? Care to talk about your use cases? If a call's better, here's my calendar.

[melgo-tb]

Hi @vihar, The issue we're encountering is that tasks are being inadvertently added to the wrong project. This typically happens when tasks are created from the "All Issues" page. By default, tasks get assigned to a certain project, which often goes unnoticed by the user. We only realised this mistake after adding all the tasks. Currently, the only solution seems to be deleting and recreating these tasks, which is quite tedious.

Is there a functionality to duplicate tasks? This feature could simplify the process of correcting such errors. We initially needed to transfer issues between projects because they were mistakenly added to the incorrect project.

[vihar]

Thanks, @melgo-tb, for the insights. Here's a summary to address these points:

• We've noted that when creating issues from the 'All Issues' page, the user experience could be enhanced. Specifically, it should be clearer which project the issues are being added to.
• It's important to enable switching issues between projects. This way, if an issue is mistakenly added to the wrong project, users can easily reassign it to the correct one.

Regarding the idea of issue duplication, this feature is already available on the platform. Here's how you can use it:

• In any project layout, right-click on an issue and choose Make a copy.
• A modal will appear with all the issue details. Simply update the project key in the top-left corner.
• This action will create a duplicate of the issue in the selected project.

While this method currently serves as a hack, we'll work on making this experience better.

[athornfam2]

Adding that I was looking for this feature as well. Whether its projects or different teams I've used this often in Jira.