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

[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. 

4. 

[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.

[Richard Davis]

Hi - please see reply under Marc's similar response