Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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,

Lorenzo

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.

Regards,
Earl

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.

Regards,
Earl

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

168 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you