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

Sub-task creation when customer Bug is Resolved and Service Case ID not empty

Iro Karavasili

Hi all,

I need your help with an issue.

When a Bug is transitioning to Resolved with Resolution=Fixed and Service Case ID not empty, a user wants to have a sub-task ticket automatically created with the following fields:

- Summary: Dev Automation needed

- Assignee: the developer of the parent Bug

So, here are what I have done till now:

Firstly, I would like to know how can I create the field Summary: Dev Automation needed. See:

User wants the subtask to be created only when Service Case ID is not empty. So, how can this be done? Now, when this field is empty we take this error:

I tested and found the following:

The assignee of the Sub-tasks was not as expected (owner was set to the project owner)

(I am new here and I am not really familiar to such requests)
Thank you in advance!
Iro

Accepted answers

Tarun Sapra

Hello @Iro Karavasili

It seems you are usign both addons Script Runner and also JSU.

Both are nice adorns but I have achieved a smilar functionality only using SR plugin.

Below the screenshot of the "create subtask" post-function of the addon

All comments

Tarun Sapra

Hello @Iro Karavasili

It seems you are usign both addons Script Runner and also JSU.

Both are nice adorns but I have achieved a smilar functionality only using SR plugin.

Below the screenshot of the "create subtask" post-function of the addon

Tarun Sapra

In the condition section you can enter the condition based on your requirement

User wants the subtask to be created only when Service Case ID is not empty. So, how can this be done? Now, when this field is empty we take this error:

if(cfValues['<Service Case ID>'] ) {

return true;

} else {

return false

}

Tarun Sapra

And in the additional issue actions just set the summary

issue.summary = 'Dev Automation needed'

Iro Karavasili

@Tarun Sapra, I filled the "condition" and "additional issue actions" fields as you said but this time subtask did not be created at all...

Iro Karavasili

What about this problem:

When I create the bug the assignee was set automatically the project owner.

Tarun Sapra

When you say

" - Assignee: the developer of the parent Bug"

WHat do you mean by developer of parent bug, is it user picker custom field from which field of the parent bug will the sub-task pick up this information as to who is the developer working on the back, which field has that information?

Iro Karavasili

I mean this field:

It works fine.
The problem is that the moment I create a Bug issue, automatically the assignee=project owner...

Tarun Sapra_2ab78x

The default assignee is always the project lead if the setting in your Jira is such that you can't have "unassigned" issues. You can add "assignee" field on create screen to add assignee manually or use a component and make component lead as the default assignee. Possibilities are quite a lot in jira

Iro Karavasili

Hello,

I would like to find a way to check if a sub-task already exists prior to creating one with the same title.

The criteria is to not create a sub-task if another one with the same summary is found.

Kind regards,
Iro

Tarun Sapra

Hello @Iro Karavasili

It would be great if you could create a new question instead of commenting on an old closed thread.

Thanks

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server