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

Create Linked Issue Problems

Atakan Olgun

Hi everyone Atlassian Admins,

We have a few projects that we use in the Jira Cloud - Software environment. Our problem is; when we want to open a new issue depending on an issue, the fields filled in the previous issue are not automatically filled. It was working before, but we have been facing this problem for a few days. Therefore, we are losing time by filling in the empty fields again when a new issue is opened depending on the issue.

In addition, I also looked at the fill rate of our automation rules, but no problem was seen.

How should I proceed for this reason? Or which rule should I rewrite again?

Best Regards,

Atakan OLGUN - Senior Support Specialist / Atlassian Admin
Gozen Digital Aviation

Accepted answers

All comments

Jack Brickey

Hi @Atakan Olgun , without seeing the rule that is being used to create issues, it will be difficult to help you troubleshoot your problem. Would it be possible for you to share an image(s) of your rule? I would also be interested in the audit block. If the audit log is indicating that the fields are being properly filled in, then it would be strange to not see them as such.

Rudy Holtkamp

Hi @Atakan Olgun ,

I've checked this in several sites I've. It only works in service projects. it does not work in software and business projects. So if this previously worked for you, you need to submit a support request at https://support.atlassian.com/contact/#/

Rudy Holtkamp

@Jack Brickey it is not a rule, but default behaviour when you create a linked issue.

Atakan Olgun

Hi @Rudy Holtkamp

This is actually a system that worked before. It was the same in the software project as it was in the Service Desk. Have certain rules changed?

Atakan Olgun

Hi @Jack Brickey

As @Rudy Holtkamp said, it's normal behavior. I didn't create a rule for it.

Jack Brickey

Yes understand. I was initially confused by your OP.

Rudy Holtkamp

I'm not aware of any changes about this. I assume this is a bug.

halil_cicek

It is evident that there is an issue we are currently facing. To address it temporarily, we have implemented an automation rule; however, we understand that this is not an ideal or long-term solution.

We have already reached out to the support team, and we remain hopeful that they will identify the root cause of the problem. At present, our automation budget is being consumed for a simple action that should have been executed by the system as part of its standard functionality.

I wanted to document this here in case anyone has insights or potential solutions related to configurations we might have overlooked.

Thank you in advance for your input.

Rudy Holtkamp

👍Please keep us posted, if/when Atlassian solves it.

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