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

Specific Approvals Workflow Help

Keratoconic

Hello Atlassian Community,

I have a very specific workflow I'd like to try and get up and running.

When a new issue is created and if the approval field is not empty then move the issue to waiting for support, but only do this if the reporter is different than the approver (we don't want users auto approving their own requests)

If approver = reporter than we'd want the automation to mention the user in a comment letting them know that this request requires for them to enter their managers username on the request (approver)

Then reject this request if this last condition meets.

Hopefully this makes sense

Accepted answers

All comments

Trudy P Claspill

What is happening to an issue when it is rejected? Is that another type of status change?

TRIGGER: Issue Created
CONDITION: Issue Fields Condition
  Field: Approval
  Condition: is not equal to
  Value: EMPTY

CONDITION: If/Else 
  IF: Advanced Compare
    First value: {{triggerIssue.reporter}}
    Condition: equals
    Second value: {{triggerIssue.approval}}

    ACTION: Comment Issue

    ACTION: (the action need to indicate the request is rejected)

  ELSE:
    ACTION: Transition Issue
      Destination Status: waiting for support

Keratoconic

Hello @Trudy P Claspill - Yes, when rejected it would move to a new status called cancelled (with a resolution)

Trudy P Claspill

Then in the above rule where I put

ACTION: (the action need to indicate the request is rejected)

...you would use the Transition Issue action to transition the issue to cancelled and set the Resolution in the same step.

Keratoconic

This didn't work for some reason, I want to clarify that on the initial step it should move them to waiting for approval, not waiting for support. I have made that change though but it's still sending it straight to waiting for approval, it might not be reading the {triggerIssue.reporter}} and {{triggerIssue.approval}} correctly?

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