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

Link issue, About "Auto Reporter"

Barış Özer

hello everyone,

Before the update to Jira:

When we made a "link issue" from a Service Desk project to another project, we were the "reporter".

Now it has changed itself.

Example:

Project = Service Desk : reporter A

issue link = project Developer : reporter A

It used to be like this:

Project = Service Desk : reporter A

issue link = project Developer : reporter B (it was me because I created the issue link)

I want it to be like option 2.

The person who initiates the link issue process must be a reporter.

Can you help me?

Accepted answers

All comments

Kristján Geir Mathiesen

Hi @Barış Özer

Have you looked at the Automation rules?

Or post-function in the workflow?

What do you mean by "Before the update to Jira" - were you on Server before?

HTH,
KGM

Barış Özer

Hi @Kristján Geir Mathiesen

I looked at the automation rule, but nothing changed/deleted.

it could be a post-function maybe yes but we didn't make any changes?

How can I add a post-function so that I am the reporter when there is an issue link?

Jira update so,

Some fields, such as "field and approval", were replaced on Jira Cloud last week.

I thought that's why I have this problem.

We are currently using Jira Cloud. It's not a server.

I show how it should be in the screenshot.

"When I make an issue link I should be the Reporter."

Kristján Geir Mathiesen

Hi @Barış Özer

Thank you for the info.

I wouldn't think there is any relation or change to the reporter even though the field is on the screen. I would think that you have to manually change the Reporter, since you are not aware of any automation rule.

What happens if you manually update the Reporter field while linking?

HTH,
KGM

Wasila Aziz Ali

We seem to be experiencing the exact same issue, and we do not have automation running of any kind on our service desk.

Was there an update made, because we noticed this happening since last week.

The problem is not everyone will remember to change the reporter when linking a ticket and therefore they do not get any responses when the linked ticket is updated, this is causing a huge delay on our side.

Thank you

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-service-desk

jira-service-desk-cloud

jira-cloud

issue-link

jira-service-management-cloud

jira-service-management