gain issuelinks

[arno]

Hi all

I recently used scriptrunner plugin to implement some automation operations. Now I have a need to determine whether the current jira issue has a related issuelink and do some automation operations.

I want to make two judgments, to judge whether the current jira issue has issuelinks, or to do some operations when issuelinks is TEST-xx. Can you tell me how to write this judgment statement

[Tim Kopperud]

Hi @arno 

You can solve this by using Atuomation. Below I have attached a rule that shows the principles on how to build this.

The trigger and the filters you will need to adjust according to your need, because I don't have enough details to include any more in the example. . 

Try this, and if you have further question about this example (e.g., needed filter etc.) please post a comment with the question and furter details. 

TimK

[arno]

Hi @Tim Kopperud 

Thank you for your reply

This is a good solution, but unfortunately our Atuomation is not the professional version, and many features we can not use

Our initial requirement is to make judgments when a jira issue is created, and after certain conditions are met, create an issue in another space and associate the two issues (e.g. cloned). This function is implemented by the listeners of the plugin scriptrunener

However, in our actual use, data duplication, which is as follows:

We have two Spaces (A and B), customers create issues through space A, our engineers create issues through space B, and issues created in space A and B will be created and associated in space C if conditions are met. Sometimes the issue created by the customer in space A and the issue created by our engineers in space B are the same issue, and the two issues will be manually associated, and we hope that in this case, only one issue will be created in space C, not two

I don't know if you can understand what I mean, it seems that automation is easier to use and more suitable for our needs, but unfortunately, we will not consider buying the professional version of automation for the time being

[Tim Kopperud]

Hi @arno 

Do I understand it correctly that you have "Automation for Jira - server Lite"?

The yellow IF filter in my image is the same as the orange JQL condition in your image, which is enabled. 

For Actions, is the Branch action disabled in your version? If it is enabled you have what's needed to build the same as in my axample. 

Let first see if you have the needed features in your version, and I will see if we can solve your requirements. Please attach images of both Trigger and Actions (as you have allready with New condtion) in a new comment. 

Edit:

Looking further into the requirements, I can say I do think I understand what you try to accomplish.  

TimK.

[arno]

Hi @Tim Kopperud 

Thank you for your reply

We do have this plug-in. Our current version is 7.2.8, but I haven't found the corresponding Branch management. I don't know if this version has this function. You are right, we do have the option to select "JQLcondition", the orange in the figure represents the features we can use

[Tim Kopperud]

@arno, If you have the oppertunity, please attach an image of your automation Actions. It seems I cannot find what limitations affects the lite version. We might can configure the rule differently.

(The supported version of Jira server ends February 2, 2024. When/If you upgrade to Data Center Automation for Jira full version is included. Same with the cloud version.)

TimK

[arno]

Hi @Tim Kopperud 

The following are the trigger, condition and action that we can use. The gray one represents the function that we cannot use, and the other colors represent the function that we can use. What else do I need to add

[Tim Kopperud]

Hi @arno 

Sorry, since Create issue is not included in your version I don't think we have any way to solve this.

If ScriptRunner isn't an option anymore I will mention the following as a possible, but unlikely, workaround:

Earlier we could install the free SIL Engine SIL Engine for Power Suite | Atlassian Marketplace. But after Atlassian closed the app purchase for server versions, I don't think you will be able to activiate it. If you have a test site you might try, and if it works you could solve your requirements by using the createIssue function etc.

TimK