Colors on Kanban-Board Column-Heads

[toba]

Where are the colors (Gray, Blue, Green) on the Kanban-Board Column-Heads??

How can I get this back?

[Felipe Silva · Accepted solution]

I also still see the colours - which relate to the status category - but only when editing the columns. I don't recall them ever showing these colours in the actual board.

[Tomislav Tobijas · Accepted solution]

Hi @toba ,

Can you maybe share on which types of projects you have seen this? Was it business or software and was it on company-managed or team-managed projects?

Additionally, you could check which changes were rolled out to your site if you're Org admin by navigating to admin.atlassian.com > Apps > App updates.

One more thing is that column colors are still visible when you go to board settings > Columns but I don't recall seeing those colors on the active board. 👀

Cheers,
Tobi

[toba]

Hi Tobi,

it’s a Business project (Jira Work Management), team-managed.

Best regards,
Thomas

[Tomislav Tobijas]

Got it @toba. Thanks for clarifying!

I haven't been using team-managed projects that often so I can't say how it was before. I've tried checking in app updates (mentioned above), but there's no change/improvement listed there related to what you're describing.

What I usually do in these cases is contact Atlassian Support and ask for clarification and confirmation of the update. For example, today they have changed one system icon for work type, which caused quite a confusion in one instance we're managing 😅

I'd say the same would apply for this: https://community.atlassian.com/forums/Jira-questions/Re-Re-confetti-animation/qaq-p/3088006/comment-id/1141488#M1141488

I'm usually avoiding team-managed projects, so I'm of no use here, sorry!

[toba]

Hi Tobi,

thanks for getting back to me and for checking the app updates — really appreciate it! I like your approach of reaching out to Atlassian Support in cases like this, and I might follow that path as well.

You mentioned that you usually avoid team-managed projects. I’m curious — what makes them problematic in your experience? I’d love to hear your take on the main drawbacks.

Also, you said that a simple change of a system icon caused quite a bit of attention. That’s interesting — what makes a change like that stand out so much in practice?

Thanks again for your time and for sharing your insights!

Best regards,
Thomas

[Tomislav Tobijas]

You mentioned that you usually avoid team-managed projects. I’m curious — what makes them problematic in your experience? I’d love to hear your take on the main drawbacks.

From my experience, it's not a bad starting point but then at one moment, users say "but we want same workflow/process as another team," which then requires migration from team-managed to company-managed project. Even though it's not that complicated, it might be easier just to start with company-managed in the first place.

However, I did attend one braindate in Team'25 this year and there were a couple of decent arguments why/when you could use team-managed projects. > From my experience, you could use those to onboard new users (project admins or Jira admins) as it's relatively easy to update configurations such as workflows.

Also, you said that a simple change of a system icon caused quite a bit of attention. That’s interesting — what makes a change like that stand out so much in practice?

In this particular case, we had a work type that was one level above Epics and as all items need to have a parent item (incl. Epics), this was noticed quite quickly. People usually don't like change 😅 and this also causes a bit of a problem as the new icon for this work type was the same color as the icon for Epics so we wanted to distinguish those two.