With Automation Create JSM ticket and set Request Type in Jira Cloud

[Nino Barnovi]

Hello,

With Automation we want linked and create new issue to each other project in Jira service Management.

We want to create New JSM ticket and set Request type.

Also, I know automation has the rule  “Create issue with a request type” , this specific rule I can’t use because here are not   “Reporter” and “Assigner”  fields.  

For that I think use the rule   “Create issue” and I want to write little logic in  More options >>> Additional fields

 I tried several options, unfortunately they don’t work.  

Project from= Trade Operations

Project to = TSTPRO

Request type= “კონტრ-გარანტია”, (in Georgian)  id="1433 "

1.  { "fields": { "customfield_10010":”TSTPRO/კონტრ-გარანტია" }}

 2.{"fields": {"customfield_10010":{{issue.customfield_10010}} }}

3.{ "fields": {   "customfield_10010":”TSTPRO/ id="1433 "   }}

Please,  text me how can I set Request type for linked issues.

I have a question: the project where I want to create and linked an issue, we have to same Request type name?   

 

Best regards

Nino

[Ste Wright · Accepted solution]

Hi @Nino Barnovi 

Can I confirm why you can't use the "Create Issue with Request Type" option?

Via Global Automation, that Action would allow you to do what you want - what is it about the Assignee/Reporter which makes this not possible?

---

You have 2 options as far as I can see:

• Use the "Create Issue with Request Type" option - then use a Branch to populate the other values (Assignee, Reporter, etc)
• Use Create Issue/Clone Issue to create the ticket - then use a Branch to modify the Request Type

This is how each might look at a basic level:

• Action: Create Issue with Request Type
• Branch: Related Issues
  • Type = Most recently created issue
    • Branch-Action: Edit Issue
      • Field = Assignee
      • Field = Reporter

OR....

• Action: Create Issue / Clone Issue
• Branch: Related Issues
  • Type = Most recently created issue
    • Branch-Action: Edit Request Type
      • Type = Value Here

---

On your separate question down the bottom, Request Types are Project-specific - so if you want to use the "same" type in the target Project, it'd need to be replicated in there.

There's a feature request you could vote for though - check out: JSDCLOUD-1317 

---

Let us know if this works!

Ste

[Nino Barnovi]

hello

First of all,  thanks everyone for a recommendation 

I Tried, your option   @Ste Wright   , and this works best, 

the Automation edited reporter and assigner fields  according with parent issue  in target project.

"Create Issue with Request Type" 

• Action: Create Issue with Request Type
• Branch: Related Issues
  • Type = Most recently created issue
    • Branch-Action: Edit Issue
      • Field = Assignee
      • Field = Reporter

I have a question: if we have create/link several  Request Types, can we make only one automation and those roles  separated each other of a branch/rule, and how?  or we have to make independent rules for specific request type?

Best regards

Nino

[Nino Barnovi]

[Ste Wright]

Hi @Nino Barnovi 

For the multiple creations - is it...

1. One additional ticket being created, but the parameters are conditional (eg. if A = 1, create B, if A = 2, create C, etc), or...
2. Multiple additional tickets being created sequentially (eg. Create, A, B, and C)

...?

---

Option 1

This should work...

• Condition: IF Block
  • IF...
    
    • Condition: Relevant Condition here
      • Action: Create Issue with Request Type
        • Branch: Related Issues
          • Type = Most recently created issue
            • Branch-Action: Edit Issue
              • Field = Assignee
              • Field = Reporter
  • ELSE IF...
    • Condition: Relevant Condition here
      • Action: Create Issue with Request Type
        • Branch: Related Issues
          • Type = Most recently created issue
            • Branch-Action: Edit Issue
              • Field = Assignee
              • Field = Reporter
  • ...etc

---

Option 2

Stacking the Actions should work in this instance.

You could use the Action "Re-fetch Issue Data" to try and keep the requests in sequential order, if this is of benefit.

For example, the rule might look like this...

• Action: Create Issue with Request Type
• Branch: Related Issues
  • Type = Most recently created issue
    • Branch-Action: Edit Issue
      • Field = Assignee
      • Field = Reporter
• Action: Re-fetch Issue Data
• Action: Create Issue with Request Type
• Branch: Related Issues
  • Type = Most recently created issue
    • Branch-Action: Edit Issue
      • Field = Assignee
      • Field = Reporter
• ...etc

---

Let us know which one you needed, and if it works for you!

Ste

[Joseph Chung Yin · Accepted solution]

@Nino Barnovi -

I agreed with @Ste Wright suggestion, we utilize the option - after the "Issue Created" trigger, then utilized the action setup to create issue in the target project below -

• Action: Create Issue with Request Type
• Branch: Related Issues
  • Type = Most recently created issue
    • Branch-Action: Edit Issue
      • Field = Assignee
      • Field = Reporter

The key configure that you also needed is to also create the proper condition(s), the the action of create issue with request type action only be executed properly and not executed for all the issues created in your original project.

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Ezgi Bayındır · Accepted solution]

Hello @Nino Barnovi ,

If you create the automation rule within the JSM environment, you can see the custom actions for the JSM. Using the Create issue with a request type action, you can create a new JSM issue by setting the request type, and you don't need to use smart value.

Best,

Ezgi