Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bulk change new version does not allow Tempo Account field update

Sarah James
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 2, 2026

I was using the new bulk change that's embedded directly in filters to try and bulk change our Tempo Account field.  When I searched the Account field I got a message that update of this field was not supported.

I then went to the legacy bulk change and was, thankfully, able to change that field immediately.

I checked all the possible issues that Rovo presented and all things indicate that the bulk change should be available.  It's concerning to me that the two versions of bulk change operate differently.

Has anyone else experienced this and if you talked to Atlassian, what response did you get?

1 answer

Suggest an answer

Log in or Sign up to answer
0 votes
abhishek_sharma03
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 2, 2026
Sarah James
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 3, 2026

 I'm not sure exactly how this article relates since it's about display in the item view, as are the related improvements?

I can easily find the Tempo account field in the filter column options and display it, the problem is with editing once it's displayed.

Are you saying that the AbstractSingleFieldType class impacts not only the view but the editability?  

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events