Automatically create issue

[arno]

Hi all

   We have recently created A new space to record some information. We hope that when certain conditions are met in space A, we can automatically create an issue in space B and associate it. Is there any way to solve this problem

[Brant Schroeder]

@arno You can use automation to to do this.  You can specify the condition and when that condition is met the automation will fire off and you can use the clone issue action to create the new issue in the other project. 

[arno]

Hi @Brant Schroeder 

Thank you for your reply

According to your suggestion, I have checked. The create issue and clone issue on automaiton we use are gray, which seems to be caused by the license expiration. Is there any other way to realize it

[Brant Schroeder]

@arno Do you have any other apps like scriptrunner or JSU?  If you do it could be done in the workflow.

[arno]

Hi @Brant Schroeder 

   We have scriptrunner, can you tell me how to automate issue creation with this plugin

[Brant Schroeder]

@arno you will need to add a post function to a transition in the workflow.  You might even add a transition that is clone issue.  In that post function you can use the Clone Issue post function documentation can be found here: https://scriptrunner-docs.connect.adaptavist.com/jiracloud/post-functions.html 

[arno]

Hi @Brant Schroeder 

Thank you for your reply 

I am trying to use the method you provide, I have a question to ask you, I want to set some judgment, when the components for certain values trigger automatic creation, this conditional statement should be written

[Brant Schroeder]

@arno You can click conditions and add something like 

'ComponentValue' in issue.components*.name

[arno]

Hi @Brant Schroeder 

Thank you for your reply

I encountered some problems in the configuration. The condition I set is to trigger when the problem is created and the module field is "11". The relevant configuration is shown in the figure

When I tried to test, I found that the plugin would constantly create new monads, which even affected the use of jira. At the same time, I found that the monads created were not linked together, is there a problem with my configuration? Can you tell me how to optimize it

[Brant Schroeder]

@arno what monads are you seeing?  I am wondering if it is something else on your server instance.  Do you see them on an issue create when not using scriptrunner?

[arno]

Hi @Brant Schroeder 

I made sure that when I close scriptrunner, the issue will no longer be created, which is indeed created by the plugin

[Brant Schroeder]

@arno What are the specifics about the error you are seeing?  Are you seeing them in the logs?

[arno]

Hi @Brant Schroeder 

I did not see the relevant error. In addition, I found that the same Settings run normally in the test environment. Is this related to the version of my plug-in? The version of the plug-in in the test environment is 6.24.0

[Brant Schroeder]

@arno possibly.  What version is in PROD?

[arno]

@Brant Schroeder  6.51.0

[Brant Schroeder]

@arno if you have a way to do a roll back in test I would suggest upgrading test and seeing if it is the issue.  If it is you would need to submit a support issue to Adaptavist.  If you do not have a way to roll back test I would suggest submitting a support issue to Adaptavist.  

[arno]

Hi @Brant Schroeder 

Thank you for your help

I will ask them for corresponding technical support. In addition, there is another question I would like to consult. I need to judge the organizations information in JSD for my judgment conditions

[Brant Schroeder]

@arno Can you provide me a little more information about judgement conditions and how you would normally do this, what is the process?