I've setup a Jira automation to assign the value of a user picker field to the current value of assignee when a PR is created and the issue is in-progress.
I've been getting this error for some time now.
"Unknown fields set during transition. Field may not be on transition screen. Fields ignored - Developer"
Originally the solution suggested here pointed me to an issue stating that due to the fact that the field was empty, it was not "seen" and therefore was not updated.
I then updated all issues to a default value however, and I am still getting the same error in my jira automations.
Below is the current result of the "Where is my field" workflow despite the error in my jira automations.
Project and issue type scope
|Field 'Developer' is in scope of the project 'XXX Product' and issue type 'Story'|
|The 'Developer' field is enabled by the 'Default Field Configuration' field configuration associated with this issue.|
|The field 'Developer' is present on the screen 'XX: Scrum Default Issue Screen' configured for this issue|
|Field 'Developer' has value for this issue|
I've also double checked all the screens on the "ViewFieldScreens" page in Jira Admin, and the Developer field should be present on all of them. What's the cause of this issue and what can be done to ensure that the field is set on this transition screen ("from in progress to code-complete")?
Hi @afenn -- Welcome to the Atlassian Community!
For a question like this, please consider posting an image of your rule and the audit log. That can give the community context to offer ideas. Thanks!
This is the second instance of this symptom I have seen posted today... Interesting...
If you have already checked the permissions, you may also check the workflow to see if there any rules trying to do something unexpected.
If that doesn't help, I suggest asking your site admin to submit a defect to Atlassian to take a look at your instance: https://support.atlassian.com/contact/#/
@Guillaume De Smedt The issue appears to be with the "transition issue" action. I noticed that I was able to set this field on another automation rule.
Therefore, I think a workaround is to simply add a step after the transition step to update the field as opposed to trying to set it in the transition step.
Hi Bill, I was contemplating it, however, meant spending time figuring out the right syntax :) - so took the easy route of simply creating another step.
The positive spin is that it's simpler to follow for other colleagues on my team to follow what's happening (2 actions in 1 step could be missed).
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events