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

Jira automation

Rajan Dangol

Hi,

I am getting the following error within sub tasks automation "Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status)". However, the email is sent.

Automation requirement:

1) Sub tasks is created.

2) When value changes for assignee

3) Issue type equals sub- task.

4) Then transition the issue to Pending.

5) Then send email.

I think the issue is failing because the issue is reassigned after being assigned the first time.

Accepted answers

Hans Polder_7ci2ta

@Rajan Dangol ,

Generally speaking, the error message states that the status 'Pending' does not exist in the workflow for the issue (type) in question.

Can you paste a screenshot of the workflow that is assigned to Sub-tasks in this project?

All comments

Rajan Dangol

Jira error 2.png Jira Error.png

Hans Polder_7ci2ta

@Rajan Dangol ,

Generally speaking, the error message states that the status 'Pending' does not exist in the workflow for the issue (type) in question.

Can you paste a screenshot of the workflow that is assigned to Sub-tasks in this project?

Rajan Dangol

Jira workflow.png

Rajan Dangol

I think the initial ticket has been assigned, the ticket is changed to Pending and then when it reassigned the ticket is already in Pending, hence the error. I think.

Hans Polder_7ci2ta

Could it be that the affected issue was already in status Done, hence it couldn't go to 'Pending'?

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

jira-service-management