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

JSM->JIRA Remote Issue Creation

Srikanth Ganipisetty_0hsoyh

Please find my requirement below:

1) Create a JIRA Issue from the JSM by cloning all the values.

2) Place a comment in JSM parent ticket with the "JIRA ID"

3) Add a validator that this script should create a JIRA ticket only once, if there's one already existing.

Please advise on how to configure the automation rules for it?

Accepted answers

All comments

Srikanth Ganipisetty_0hsoyh

Updates?

Joseph Chung Yin

@Srikanth Ganipisetty -

What are you trying to accomplish? Are you trying to create a new Jira software issue and link it to the parent JSM issue? If the parent issue already linked to an existing Jira software issue, then don't create another issue in Jira software project?

If so, you can just use Automation for Jira to create an automation rule to conduct the activities without using the complex scripts that you are using via post-function calls in the issue's WF.

Please advise.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Srikanth Ganipisetty_0hsoyh

Hi @Joseph Chung Yin

Please find my requirement below:

1) Create a JIRA Issue from the JSM by cloning all the values.

2) Place a comment in JSM parent ticket with the "JIRA ID"

3) Add a validator that this script should create a JIRA ticket only once, if there's one already existing.

Please advise on how to configure the automation rules for it? We have this existing script and wanted to use for it any future projects. This script is working fine on console with 0 issues, but it is failing with "NULL" value when we run through post functions/Automation-for-rule> Run a script runner action process.

Srikanth Ganipisetty_0hsoyh

@Joseph Chung Yin any tips?

Bhuvaneswari Vasudevan

I have a similar situation.

There would be tickets raised in JSM by end users when we launch the product. The ticket will be in the Service project. This needs to be cloned as issue in the Jira Software project for the application team to look into as part of their kanban/scrum board. This issues should be linked in the ticket so that we can track to closure. Any suggestion on how I can implement this.

Amal P

@Srikanth Ganipisetty @Bhuvaneswari Vasudevan Have you fulfilled the requirements mentioned here?

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-service-management

jira-service-management-server