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 Failing Since Projects became Spaces

Richard Davis

Since the rebranding of Project to Spaces, all of our automations have been partially failing with "The set fields may be unavailable for this space/type" error. This looks to relate to a custom field set via the JSON part of the Create Work Item action.

These were all working before the change, and nothing else has changed (from our side, anyway).

Has anyone else come across this?

I have checked historic posts about this, and I assume it is probably to do with the actor being "Automation for Jira", but I can't find any way to correct it.

Thanks,

Richard

Accepted answers

Richard Davis

The fix was to explicitly add the field in the Request Form for each work item type (ie. the form where a user would create a request) - I don't know why exactly this is now needed for creation via the automator, but it seems that it is.

All comments

Kai Becker

Hi @Richard Davis

thanks for you question. Could you please share a screenshot of your rule configuration and the audit log error.
This will help to identify and resolve the issue.

Marc -Devoteam-

Hi @Richard Davis

Please show a rule as an example and provide from this rule:

1. what type of project is this (e.g., company-managed, team-managed, etc.),

2. images that show your complete rule.

3. images showing the details of any relevant actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. Explain where the issue is.

These questions are not for not willing to help, but to have community members understand on how automation works.

On topic, this should not have to do with the actor, unless the actor has no rights on the project anymore.

Richard Davis

Hi,

Thanks for the quick response (and also to Kai, who has asked similar questions)

1. I'm not actually sure - we only have a small Jira instance with a single Space (aka project).

2/3. {341CC74D-C62B-4FC7-A3D8-C8C5445C3E52}.png

{48BAA880-CF88-4941-8529-149DD6A00A84}.png

4. {5EDF1734-9513-41D1-8358-8F60E7703D6C}.png

Richard Davis

Hi - please see reply under Marc's similar response

Ben Drew

@Richard Davis did you ever resolve this? I am having similar issues.

Richard Davis

Hi @Ben Drew ,

Yes, we did get it working in the end with the assistance of Atlassian support. The fix was to explicitly add the field in the Request Form for each work item type (ie. the form where a user would create a request) - I don't know why exactly this is now needed for creation via the automator, but it seems that it is.

HTH!

Richard

Richard Davis

Ben Drew

Thanks @Richard Davis , I had just stumbled across this article Automation | Error : Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Reporter (reporter) | Automation | Atlassian Support which also aligns with your solution. Many thanks for the quick response!

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

spaces