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; } } }

Audit Log

Kim Killen

Morning. Can someone please fill me in regarding the meaning of operation details within the audit log?

Event Category: issue type scheme

Change Summary: Issue type scheme updated

Changed Object: Default Issue Type Scheme (migrated 3)

Then Operation Details: See screenshot below

Associated to Projects: lists hundreds of project ID's with a strikethrough

Associated to issue type(s): All issue types

What does the Associated to project(s) tell me? When this change was made were these the affected projects? And the strikethrough indicates the change was made to said project?

Thanks. Screenshot 2024-04-04 091514.png

Accepted answers

Rebekka Heilmann (viadee)

Hi @Kim Killen and welcome to the Community,

it looks like someone dis-associated all these projects from said Scheme. By dis-associating projects from a custom Issue Type Scheme, they will be associated with the Default Issue Type Scheme automatically as every project needs to be associated to one at all times.

By the name and the number of the projects I guess this has been a cleanup action by one of your admins, moving the projects from a temporary scheme back to the Default?

Red and striked-through = deleted -> in this case dis-associated

All comments

Rebekka Heilmann (viadee)

Hi @Kim Killen and welcome to the Community,

By the name and the number of the projects I guess this has been a cleanup action by one of your admins, moving the projects from a temporary scheme back to the Default?

Red and striked-through = deleted -> in this case dis-associated

Kim Killen

To confirm, you're saying that all of these projects were dis-associated from Default Issue Type Scheme (migrated 3) and because they have an unassigned scheme, they're automatically associated to whatever our default scheme is?

If so, how do I fix it?

Rebekka Heilmann (viadee)

The Default Issue Type Scheme contains all Issue Types that are configured in your system and cannot be edited. Hence the name "Default"

The projects are never unassigned - they were moved to the Default scheme immediately with no state in between when they were dis-associated from the "migrated 3" scheme.

You can associate the project(s) with different schemes: Associate issue types with projects | Atlassian Support

Kim Killen

So you're saying our default scheme is NOT "Default Issue Type Scheme (migrated 3)"?

All of those projects were dis-associated from the migrated 3 scheme? How can I tell which scheme they are now associated to? OR to ask another way - how can I tell what scheme is our true default scheme?

Sorry, I'm new to the company and trying to learn Jira at the same time as trying to manage Jira. There's no administrator here so I'm learning as I go!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud