Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Project Category reset after change of project avatar

Good day everyone,

As question suggests, I'm running in some sort of hiccup each time someone (notably: project managers) go and update the project avatar.

This operation causes the reset of the Project Category field, which is not good as I use that field for reporting purposes towards EazyBI. Without the project category to drive the aggregation, the project is discarded from the dataflow.

Anyone having the same issue, and/or able to suggest how to avoid this behavior?

Product is Jira Core in Cloud.


Many thanks in advance,


1 answer

1 accepted

0 votes
Answer accepted

Hello @Lorenzo Torresin ,

This is a known but that we are tracking at the following link, where editing the the project details while loged in as user with Project admin that does not also have Global Admin, so they can configure other details but do not have permission to se the category, so the option is cleared as the permission set thinks the user is attempting to set the category on the update:

Editing the details as a global admin is currently the only option to set this value correctly.


Thanks Earl,

Is it possible to give project admins the permission to see and edit the project Category, so that this could be used as workaround?

Hello @Lorenzo Torresin ,

Unfortunately no, to get around this one you would need to give the Project admin the global Jira Administrator permission, and there is not another way to delegate just the category to the project admin level until the Bug is fixed.

The only way to address this one without lowering the security levels by adding unneeded  global admins is to have an a global admin make edits on behalf of the project admin.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events