Create an issue in another project using a custom field

[adam.quinn]

Hello and good day Atlassian Community!

I have a request I am attempting to solution using native automation functionality in Jira Cloud.

Background: We have a team that is reviewing significant errors and events while working with external stakeholders to remedy the errors going forward. When their review and analysis is resolved they would like the following to happen:

A automation to run that creates an Epic and Stories in the identified project backlog. We have a custom field that lists all available project (a project picker field limitation does not fit our enterprise use case)

The Hurdle I'm experiencing: The problem I'm running into is how the automation can identify and create the Epic to a dynamically identified project backlog based on a custom field. This custom field does have project key information in it (project name/project key)

I found this community post where an individual identified to use smart values and and "more options" dropdown in the issue create. However that uses a project picker field instead of a custom field.

Has anyone attempted or created something similar?

The linking of the stories pulling information from the analysis is very simple. It's the Epic creation based on a custom field that's throwing me for a loop

[Mark Segall]

Hi @adam.quinn - If your list of projects is lengthy, you can explore an option using Assets (you'll need premium JSM licensing).  Here's how it works:

In the create issue action, you can dynamically set the project and issue type.  However, you must pass the system ID.  So, you'll need an Asset scheme like this:

• Object Type 1: Projects
  • Attribute 1: Project ID (actual numeric ID value for the project asset)
  • Attribute 2: Reference to desired Issue Type (more below)
• Object Type 2: Issue Types
  • Attribute 1: Issue Type ID (actual numeric ID value for the issue type)

From there, you'd want to replace your current project picker with an Asset field that pulls in the projects from Assets.

Then your Create Issue action would look something like this:

• Project = {{issue.Project.Attribute 1}}
• Issue Type = {{issue.Project.Attribute 2.Attribute 1}}

[Filipi Lima]

Hi, Adam!

How many possible projects could this branch into?

I ask because if the number is not too high, one option would be to use if/else blocks based on the custom field value which would also give you quite a lot of customization potential for each project. Something like this:

[adam.quinn]

Thank you Filipi for you reply!

Right now the list is around 70 projects right now with the vendors and project list we work with changing weekly/monthly.

I like this idea, but I am concerned with the level of effort it would take to maintain it, also with the automation limit it would have to be spread across multiple automations.

(Great project names btw)

[Filipi Lima]

That level of creativity is beyond me :), that's from automation playground: https://www.atlassian.com/software/jira/automation-template-library/rules#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC

Yeah, 70 project is a bit to much to go on that approach, it would be perfect for 10 or so.

On the article you shared where they mention a Project Picker field, try exploring a similar approach even without that specific custom field type since you said you do have the project key on your field.

On this community post: https://community.atlassian.com/t5/Jira-questions/Use-a-Field-Smart-Value-For-Destination-Project-when-Creating/qaq-p/822356

You can see they not only lack a Project Picker field as well but they pull some string manipulation to feed the Key as an input (the manipulation will depend on how you have it set-up):

{
"fields": {
"project": {
"key": "{{issue.Random Custom Field.value.substringAfter(\"(\").remove(\")\")}}"
}
}
}