I cannot edit the columns of my own filter.

[Nicolas Gabriel Ibarra]

When the user tries to edit the filter columns of his private filter, a message is displayed stating that he cannot edit a filter that belongs to another user, but the filter belongs to him and is not shared. The user has the permissions of jira-users that allows this operation, but is not being able to do it.

[Jack Brickey · Accepted solution]

Hi Nicolas, welcome to the Community. How confident are you that this person owns the filter? Please click on the Search bar and at the bottom of the popup click Filters. Find the specific filter and see who the owner is. Be sure to check for similar filters. If they indeed are the owner please sit w/ them and have the go to this page and then have them click the ellipses to the right of the filter and see if they can Edit.

[Nicolas Gabriel Ibarra]

Hi Jack, thanks for answering, we made the user change the permission from "Private" to "My Organization" and with this we could verify that the filter really belongs to them. I want to comment that this problem started to happen after I made a migration from Jira Server to Jira Cloud. Before, this user could make the modifications in the columns of his filter when he wanted.

[Jack Brickey]

Ah I see. I can imagine that the migration might cause oddities like this. If this were to continue I would create a new filter and delete the old. 

[Nicolas Gabriel Ibarra]

Yes, it is the last option that we will take XD, create a new filter and delete the old. we created a ticket to atlassian with this problem. Thank you very much Jack for your help.

[Rene C_ _Atlassian Support_]

I know this conversation happened a while ago, but from support cases I have spotted this happening every now and then, and it was indeed caused by inconsistencies, and the easiest way to solve it is by transferring the ownership of the filter to someone else, and then back at the original owner. If you find this is happening with many filters, it might be best to raise a support case with us so we can understand if this is a latent bug or something that got broken due to a migration of data.

[Jack Brickey]

@Rene C_ _Atlassian Support_ , Thanks for sharing this workaround. Is there a JAC issue on this?

[Rene C_ _Atlassian Support_]

Since bugs are only raised when an issue is replicable (or at least considered a trend) and at the moment I have only encountered a couple of cases a few years apart which are then solved by the workaround, and those cases have also had some form or another of data migration, so this is not considered a bug at the moment, just an inconsistency (which like any inconsistency could be caused by many different reasons). In case we notice a trend, we will investigate and raise the bug report.