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

Can I automatically register a 'parent item' issue as a linked issue?

clown

When a 'sub-item' of an issue type 'Task', 'sub-bug', is converted to a 'bug' type, is it possible to create an automated statement that registers the 'bug' issue as an issue that links the previous 'parent item' issue?

Reproduction order and expected results.

1. A ‘task’ connected to B ‘sub-bug’

2. B ‘sub-bug’ → B ‘bug’

3. B 'Bug' - A 'Task' (related to) // Jira Automation

Accepted answers

Stefan Salzl

@clown

If I got your requirement correctly (as described in my answer to your last post) the following rule should do the work

Whenever a Sub-Bug is converted to a Bug an issue link between the (new) standalone Bug and its former parent issue is created

(the issueType condition is optional - if added it needs to be configured regarding your conditions)

As you can see in the "link issue" action a smart value is used for the issue to be linked at (which is the former parent):

{{fieldChange.fromString}}

Please give it a shot and let us know if it works or if there are any further questions. In case there are any further problems please provide some material for analyse like screenshots of your rule and audit log

Best
Stefan

All comments

Marcos Defina

When a subtask is converted to task, or a sub-bug is converted to bug - their Parent field is cleaned.

You can use this as a trigger.

Now, to recover the previous parent with no external script will be a problem.
If you are able to script in python, you can create a listener to this event and previous parent information from the history.

But if not, you can create a custom_field (lets call it last_parent) that would hold parent information during creation. Just create a post-function to update your last_parent to the current parent on sub-task creation time - in this way you will be able to recover last_parent once the sub-task gets promoted to task.

Then your automation will look somewhat like this: Screenshot 2024-12-02 234338.png

When Value of Parent changes to Empty
If Issue Type In {Task, Bug}
Edit Issue Fields using Advanced Field Editing to insert current_issue.last_parent into the new issuelinks (this part will take some trying and error to get the syntax correct)

Hope it helps!

Bests,
Marcos Defina.

Stefan Salzl

Hi @clown & @Marcos Defina

there are smart values for fieldChanges. the following screenshow shows how the former issue (parent) can be fetched:

find more detailed information here:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange--

Best
Stefan

clown

@Marcos Defina cc. @Stefan Salzl

Hi, I tried it but it doesn't seem to work. The question I was asking was about attaching a "Linked Issue" instead of the "parent" automation for transitioning sub-bugs or sub-tasks.

Stefan Salzl

what did you try? what didn‘t work? could you show the result and/or your rule and the audit log of your run?

You need to get the former parent. How should the automation know where to link the „new“ issue? we were just pointing out how to manage the start. Linking need to be done in the automation.

Thanks in advance

Best
Stefan

Stefan Salzl

@clown

If I got your requirement correctly (as described in my answer to your last post) the following rule should do the work

Whenever a Sub-Bug is converted to a Bug an issue link between the (new) standalone Bug and its former parent issue is created

(the issueType condition is optional - if added it needs to be configured regarding your conditions)

As you can see in the "link issue" action a smart value is used for the issue to be linked at (which is the former parent):

{{fieldChange.fromString}}

Best
Stefan

clown

This was the result of the first answerer's solution first.
Even when I applied the answer you provided, it still didn't work.
There was no audit log left either.

Stefan Salzl

Hi,

was there no audit log? Not even an error? no execution at all?

First thing I can see kn your screenshot: your condition checking for issuetype task. As I mentioned in my answer you have to change the condition to the issuetype you are converting to. So when you gonna convert a sub-bug to a bug the condition of your screenshot will be fals therefore the rule won‘t do anything. in this case you need to change the condition to bug. The condition could even be left out at all. that would be good for tests so we know the rule is activating ar your side.

Could you please also share a screenshot of the details of your rule details as well as from your trigger details and also a step by step description what you are doing when you expect the rule to activate.

Best

Stefan

clown

Hi, Stefan! Sorry for the late reply, I was busy.
First of all, there was no Audit log, and there was no Error.

The direction I want is as follows.
When a Sub-bug, which is a sub-item of a Task, is converted to a Bug issue, a relates to link is attached to each task.

Below is the syntax written.

Thank you for your favor.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation