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

Create / clone issue when project name is smart value / dynamic

Alex Rouk

Hello, community.
Is there a way to create a new issue (or clone) without providing a specific project name?

In other words, i need a rule that can create an issue, while target project is based on a trigger' field value (assume that there is a field with the project key or name (tried both) provided by a user and can vary.

tried using smart values for both project and issue type and it fails on 'project name is required'.

i have a workaround in mind but i don't like very much.. (it requires a rule for each possible project, bunch of flags and complex maintenance )

thank you in advance!

Accepted answers

All comments

Simmo_9kntn7

Hi @Alex Rouk ,

Not sure which Automation you're referring to. But if you're referring to Jira Automation (formally Automation for Jira) then there is an option in the UI that will do what you want to acheive:

Cheers,

Simeon

Alex Rouk

Thanks, @Simmo Yeah, that Automation

My issue is that I don't want (can't) to put a specific Project name because it is uncertain when i'm creating the rule. So i wanted either to use field's value there or a variable.

Is it possible?

Thank you!

Simmo_9kntn7

Hi @Alex Rouk ,

Does the "same project" option not work for you? It will try to determine it based on the trigger context. So you shouldn't have to specify a project.

Alex Rouk

Thank you again, @Simmo .

it is not that simple..

Imagine i have a rule triggered from project A. The rule is supposed to create a new issue in another project (B, C, D..), based on a value of projectA_field. The value of projectA_field is entered by user.

For example, if projectA_field = "B", the issue will be created in B, if projectA_field="C", then in project C.
Project A is kind of a hub, creating tickets dynamically in other projects

Hope this clarifies.

thanks!

Tony Villa-Cruz_oew8y8

I think people are not seeing that this question has been answered, so I am re-posting @Italo _Modus Create_ 's answer as an answer outside of the the other answers thread, because I found that this answer does in fact work!

@Italo _Modus Create_ said:

I was able to achieve this by using the additional fields to overwrite the Project that I need to create the issue.
In my case I have a custom field named "Activity" and the options are
Task A - ASP
Task B - DSP
...

The bold section is the project that the task should be created into, so I was able to do extract the project key using substringAfter and then use to as the project key.
{
 "fields": {
   "project":{
      "key": "{{issue.Activity.value.substringAfter("-").trim()}}"
   },
   "Parent link": "{{triggerissue.key}}"
 }
}

Hope this helps people find the answer! This was a big unlock for me!

Andrej Goleniewski

Thanks a lot!

Fred Quintero

I used this post and this one: https://community.atlassian.com/forums/Automation-questions/Clone-to-a-Project-where-the-Key-is-passed-to-a-Smart-Value-from/qaq-p/1659713#U3011388

I posted an answer that worked for me here here: https://community.atlassian.com/forums/Automation-questions/Re-Clone-to-a-Project-where-the-Key-is-passed-to-a-Smart/qaq-p/3011388/comment-id/14126#M14126

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

automation