nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Project Category reset after change of project avatar

Lorenzo Torresin

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

Accepted answers

Earl McCutcheon

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:

https://jira.atlassian.com/browse/JRACLOUD-67434

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

Regards,
Earl

All comments

Earl McCutcheon

Hello @Lorenzo Torresin ,

https://jira.atlassian.com/browse/JRACLOUD-67434

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

Regards,
Earl

Lorenzo Torresin

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?

Earl McCutcheon

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-core

jira-core-cloud