kanban board columns changed

Christian Holton_1x5l5s

This is in a company-managed Kanban project. My board columns have all been replaced by column names that are irrelevant to the project. I was able to fix the two projects that were affected, but I'd like to know why this happened and how to prevent it from happening again. I checked the Audit Log and didn't find anything relelvant.

Thanks!

James Gamble

Hi Christian,

Since two boards were affected at the same time, I’d first check whether they use the same saved filter or whether someone changed which filter each board uses. A company-managed board isn’t permanently tied to one project. It displays whatever work is returned by its saved filter, so selecting a different filter can make a board appear to have inherited an unrelated configuration.

You can check this under Board settings > General. Confirm that the Saved Filter is the expected one, then check the filter’s details to see who owns it and whether it’s shared with anyone who may have edited it. Atlassian explains where that setting is here.

If the filter was still correct and the actual column names and status mappings changed, someone with board administrator or project administrator access likely edited the board configuration. Unfortunately, Jira’s audit log isn’t intended to record every action, and board column changes aren’t included in Atlassian’s published list of audited events. That would explain why you didn’t find anything relevant.

I’m not aware of a setting that locks an individual board’s column configuration. The best prevention is to limit the board administrator list under Board settings > General, avoid using broad groups where possible, and make sure the saved filter is owned by a stable admin account rather than an individual user who may change or replace it.

Since the changes appeared unexpectedly on two boards and there’s no audit record to identify the cause, I’d also open an Atlassian Support case with the board URLs and the approximate time the changes occurred. They may be able to determine from backend logs whether this was a user action or a Jira Cloud issue.

Thanks,

James