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

which automation affect particular ticket

felix.weber

Dear all,

I am facing the strange behaviour that a ticket will be created in my name however I have still not found its root cause.

basic question: I there an way to see which automation have touched an issue !?

I thought an automation is creating the tickets but there are hints (e.g. one text we use to get further details automatically contains a colleage I have never talked to (of course asked him directly already)

After reviewing all J4A I still wondering where those issues comes from.

Tried also to find them in the Automation log - but even there can´t identify an automation -however because there are running so much automation I might oversee something important

Accepted answers

All comments

Jack Brickey

Did you also inspect the Legacy Automation?

Alex Koxaras -Relational-

Hi @felix.weber ,

Tickets can be created:

By a user
By an automation
By incoming mail (& mail handlers)

My guess would be to check the incoming mail handlers, in which you can define the reporter as well.

Alex

Melo_45tw58

Hi Felix,

There are many factors and configurations items that can cause this behaviour, have you seems any pattern on the issues?

Some places to look other than A4J

Components
Legacy automation (mentioned by @Jack Brickey )
Workflow post-functions
Request type configuration (you can hide assignee from the form and set a default value)

Cheers,

Melo

felix.weber

you are right - only forgot to state this in my description

yes checked and found nothing

felix.weber

mail handler also checked - however within the ticket I saw that it states

Felix raised this request via API

which leads me again to our API but non of them even deals with this request type

Alex Koxaras -Relational-

Did you send this API request? If yes, and you are logged in then I suppose that this is the right behaviour.

felix.weber

thanks for all your comments !

to add more findings which I obviously missed to post or meanwhile figured out:

as stated in a comment above: the ticket I see that it states

Felix raised this request via API

which leads me again to our API but as we have only 1 API running this does not even though this request type.

The issue will be created everyday at 2:07pm - so checked all J4A & Legacy A. - non of those automation running shortly before are creating a issue.

Furthermore I have checked

mail handler, repetitive tasks , and workflow

For this request type related workflow was edited the last time in April, however the issues are created this 12th July - so I guess it can´t be the workflow

meanwhile I doubt that is a Jira automation creating those ticket because after the issue is created an J4A will update some fields

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-desk-cloud

addon-com.codebarrel.addons.automation

automation

jira-service-management-cloud

jira-service-management