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

Automation works across all projects, but I want only one

Blake_9lrh2u

The loom video explains to the best of my ability. Basically, my automation works great BUT unfortunately it works across all projects, and i only want it to apply to 1 project.

https://www.loom.com/share/f8544cb19b144b89862fbf24baa7720c?sid=e552d5cb-c3c9-4750-b973-67ca478ea606

Accepted answers

Bill Sheboy

Hi @Blake

There are at least two changes for your rule shown to do what you ask:

Inside the branch, move the condition to check the project is JS before the transition
Next, as the rule is written it would unconditionally move those JS work items to "In Progress". Is that what you really want, or are there other criteria, such as...
- The JS work item is not already "In Progress", "Done", etc.
- A specific link type is involved
- etc.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Blake

There are at least two changes for your rule shown to do what you ask:

Inside the branch, move the condition to check the project is JS before the transition
Next, as the rule is written it would unconditionally move those JS work items to "In Progress". Is that what you really want, or are there other criteria, such as...
- The JS work item is not already "In Progress", "Done", etc.
- A specific link type is involved
- etc.

Kind regards,
Bill

Blake_9lrh2u

That fixed it, simple! Thank you.
Well, if a JS is linked to a JS, then it should not (and currently set as such I believe) manipulate the status. only when a JOB ticket is linked. that is the goal. and if a JS is already marked as DONE, then it disappears and would be (fairly) unretrievable in order to accidentally link a JOB ticket to it, which would undesirably re-open the JS ticket into status IN PROGRESS.

Bill Sheboy

Awesome; I am glad to learn that helped.

Based on what you described in the second bullet, I recommend adding an additional condition (inside the branch) so the transition only happens when the Status is in one you expect.

Blake_9lrh2u

@Bill Sheboy,

Now ive got a new problem that arose since making this change. So now, I am getting customer replies as a new ticket. this is creating quite a huge mess. how in the world would that be happening?

Bill Sheboy

@Blake please post images of your current rule and of the audit log details here in the question using the insert photos option. Those will provide context for the symptom.

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-management-cloud

jira-service-management