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?
Hey @Sarah James - Check this article for reference - https://tempo-io.atlassian.net/wiki/spaces/KB/pages/2645458945/Tempo+Account+and+Team+custom+fields+limitation+in+Jira
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.