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

Testitng a Request Type in an automation rule

Jader Peixoto Volkmer

Hi guys,

I need your help to check if it is possible to validade a request type value in an IF clause in an automation rule. For example:

The Request type called Observabilidade needed to be validated in order to set set another field values and create other linked issues.

It doesn't work neither in the IF clause nor in the ELSIF clause.

Could you plase help me on this?

Thank you.

Accepted answers

All comments

Dan Breyen

Hi Jader, you should be able to check the request type right when the work item is created. I do that for some of my Automations. Here's a screenshot of how I'm doing it.

Hope that helps.

Joseph Chung Yin

@Jader Peixoto Volkmer

Are you setting the field's value based on the request type of the newly created issue or are you setting the values of the created link issues?

If not, you may want to use "Issue linked" trigger, and then setup the conditions to populated the field values of the linked issues (i.e. pulling values from the source issue)

Hope this also helps.

Best, Joseph

Jader Peixoto Volkmer

Hi Dan,

expanding my first test here we have:

so it looks like yours. So I don't know why this is not working.

And to make it more clear, in the agents view, here are the request type:

Tks.

Lalithesh

Hi @Jader Peixoto Volkmer

It may also be worth checking how the Request Type is being populated. If it is being added by another automation, ensure that 'Allow other automations and user actions to trigger this flow' is enabled under Flow settings

Cheers!

Jader Peixoto Volkmer

Hi Joseph,

I am testing a request type of an issue newly created. When the issue is created, test its request type and based on its value, open linked issues on another project. This is my objective.

Is there any restriction involved on testing request types? Or any kind of setting that may be missing?

Jader Peixoto Volkmer

Hi @Lalithesh , this is already checked!

This means: Allow other automations and user actions to trigger this flow.

Thank you!

Jader Peixoto Volkmer

Hi guys,

I think I solved and the solution is simplest I thought it would be (as soon as I know at this moment).

In my test project it works and I am validating in a production's one.

I'll tell you.

Welcome!

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