How to issue tickets to other Jira projects

[Inderaj Chem]

Is there any solutions or workarounds on how to populate the Project field on a new Jira ticket, using a single select dropdown custom field from an existing ticket.

Scope: In my example, I'm trying to push tickets from one project to another. I'm trying to take a custom field value and use this to populate the project field value on a new ticket via Automation.

I've used Smart Values, however it seems the project field only recognise key or project ID.

It seems to be having a problem with taking the data from a single select text dropdown e.g. Project One and converting that data into a key/ID.

[Bill Sheboy]

Hi @Inderaj Chem -- Welcome to the Atlassian Community!

What you are describing is the Jira Move operation: moving an issue from one project to another.

https://confluence.atlassian.com/jirasoftwarecloud/change-an-issue-s-project-or-issue-type-using-the-move-feature-1283493350.html

Different projects have distinct configuration, workflow, etc. and thus Atlassian provides the Move operation to guide a step-by-step interaction to reduce problems when moving issues to a new project.  (For example, asking about issue type changes between projects.)

Automation rules do not provide a step-by-step interaction feature to support a move operation, and thus the only option is to use the REST API endpoint called from the rule and to predict what is needed to help the move be successful.

Kind regards,
Bill

[Fazila Ashraf]

Hi @Inderaj Chem 

Welcome to community!

Can you explain this more - "however it seems the project field only recognise key or project ID."?

Based on https://support.atlassian.com/cloud-automation/docs/jira-smart-values-projects/ , project name {{project.name}} is feasible.

[Marc - Devoteam]

Hi 

Yes, smart values are only there for project key and id.

There is no option from project names.

The same applies if you would want to use API, you can only get info based on key or ID