change a Project on a Issue based on a Issue field

[Deleted user]

All of our bugs flow into one Project, and then folks have to add labels and use the interface to change the project to appropriate team. The interface takes a lot of clicks. Is there anyway for the Project to automatically reassign to the Project identified in a Label, or some other field?

[Ismael Jimoh]

Hi Heather,

I do not think the way you intend to implement this is the appropriate solution.

Instead, my suggestion would be creating a linked issue if the first project is meant to be a stop gap project. (Though more appropriate would be teaching people which project to create issues in).

The second would be use scriptrunner post function to clone the issue to the second project based on the field but you would need to write the script to achieve this. It has a post function that allows cloning issues into other projects that can be added to your workflow.

These are the solutions that come to mind.

Hope they help.

Regards.

[Nic Brough -Adaptavist-]

I support this approach.

Moving an issue from one project to another is not a trivial action.  This is because project is not a "field" that you can just change.  It's a critical part of the infrastructure. 

Imagine a Jira system as a street of houses, each project is a house, each issue type is a room in a house, and walls are issues.  Whilst you can easily change the fields of a wall (like colour, pictures hung on it, etc), moving a wall from one room to another is not trivial, let alone moving a wall from one house to another.

Any process that tries to use "change project" as a standard process is not a good process to replicate in Jira.  "change project" is for making organisational changes or for when someone really did create something in the wrong place.