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

Create issue automation fails due to unspecific mandatory field error

Sia (Nastassia) Sharasheuskaya

Hi all,

I'm trying to automate the following: When an incident is downgraded to a bug with the resolution "Raised as product bug" and status Declined, two things should happen:

1. A slack message is posted (this works)

2. A bug is automatically created and a comment is added with the link to the bug

Everything works except the creation of the bug, comment is added, slack message is posted but the bug is not created. I have added all the mandatory fields to the automation to pre-fill them and also added a screen that displays them and the user can update if needed. However, the bug is not created and the error in the logs is not specific, it just tells me that a field is mandatory but is not telling me which field

Accepted answers

John Funk

Hi Sia - Welcome to the Atlassian Community!

You have the fields for the Bug being copied from the Current Issue. The Bug is the current issue, so there are no values for any of those fields. You need to copy each field from the Trigger Issue instead.

All comments

John Funk

Hi Sia - Welcome to the Atlassian Community!

Bill Sheboy

Hi @Sia (Nastassia) Sharasheuskaya -- Welcome to the Atlassian Community!

It appears there is a required field for your Bug issue type that is not set. Please check what may be missing and include that when the issue is created.

Hi @John Funk

I believe the "current issue" is the trigger issue for the rule shown, and not the Bug issue which has not yet been created.

Kind regards,
Bill

John Funk

@Bill Sheboy Inside the creation of the Bug? I don't think I have ever seen that done. At the very least the trigger issue should work, should it not?

Bill Sheboy

Yes, and...the Current Issue {{issue}} changes based on scope within the rule. The Trigger Issue {{triggerIssue}} is constant throughout the rule (other than when changing for a scheduled trigger with JQL iteration).

For example:

trigger: ... Trigger Issue, Issue, and Current Issue are the same
condition: ... Trigger Issue, Issue, and Current Issue are the same
branch: to some issues (e.g., with JQL) Trigger Issue, Issue, and Current Issue are the same
- action inside the branch: ... Issue and Current Issue refer to the branched-to issue, and Trigger Issue remains the original one
action after the branch: ... Trigger Issue, Issue, and Current Issue are the same

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