I'm currently working on a Team managed project that uses a form with conditional fields to add approvers under certain circumstances. I have the form field linked to "Approvers" so anyone selected in the form field should be added as an approver. This isn't adding the users to the "Approvals" section. I tried copying the "Approvers" to "Approvals" and I can't get the users to add. I tried a bunch of different "Additional fields" JSON with no success. * { "fields": { "customfield_10035": "{{#issue.customfield_10003}}{{accountId}}{{^last}},{{/last}}{{/issue.customfield_10003}}" } } * { "fields": { "customfield_10035": { "id": "792", "name": "Urgency Approval", "finalDecision": "pending", "canAnswerApproval": false, "approvers": [ { "accountId": "{{issue.customfield_10003.accountId}}" } ] } } } * { "fields": { "customfield_10035": "{{#issue.customfield_10003}}{{accountId}},{{/issue.customfield_10003}}" } } I looked up the custom fields via XML and I see these:

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

Team Managed Approvers not linked to Approvers field

Kurtis_7ezt99

I'm currently working on a Team managed project that uses a form with conditional fields to add approvers under certain circumstances.

I have the form field linked to "Approvers" so anyone selected in the form field should be added as an approver.

This isn't adding the users to the "Approvals" section. I tried copying the "Approvers" to "Approvals" and I can't get the users to add.

I tried a bunch of different "Additional fields" JSON with no success.

{ "fields": { "customfield_10035": "{{#issue.customfield_10003}}{{accountId}}{{^last}},{{/last}}{{/issue.customfield_10003}}" } }
{ "fields": { "customfield_10035": { "id": "792", "name": "Urgency Approval", "finalDecision": "pending", "canAnswerApproval": false, "approvers": [ { "accountId": "{{issue.customfield_10003.accountId}}" } ] } } }
{ "fields": { "customfield_10035": "{{#issue.customfield_10003}}{{accountId}},{{/issue.customfield_10003}}" } }

I looked up the custom fields via XML and I see these:

Screenshot 2024-08-08 113634.png

Accepted answers

Marc -Devoteam-

Hi @Kurtis

It might this KB article will help you: https://support.atlassian.com/jira-service-management-cloud/docs/add-an-approval-to-a-request-type-in-team-managed-projects/

As I think the normal approver and approval are only used by Company managed project

All comments

Marc -Devoteam-

Hi @Kurtis

It might this KB article will help you: https://support.atlassian.com/jira-service-management-cloud/docs/add-an-approval-to-a-request-type-in-team-managed-projects/

As I think the normal approver and approval are only used by Company managed project

Marc -Devoteam-

And you are probably running in to the following limitations on team managed project in relation to automation; https://support.atlassian.com/cloud-automation/docs/limitations-in-team-managed-projects-for-automation-rules/

Kurtis_7ezt99

Yea.... I think it's those limitations.

Specifically:

Custom fields: All People custom fields in team-managed projects currently aren’t supported by Jira Cloud automation. This means that your automation rules won’t be able to access values or set values in any People fields.

That's a bummer.

Thank you for the links!

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