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

How to trace unexpected changes in issue types?

Pascal Rieux

Hi,

On JIRA 6.4.6, we are currently facing a situation where a default issue type name is unexpectidly changed to another (and existing) issue type name. After having activated TRACE logging on the {{com.atlassian.jira.web.action.admin}} package, nothing appeared in the logs.

Is there any way to find from where (add-on? automation? other?) this change comes from?

Note that, be it on the database side or from the REST API, everything looks fine, names are kept unchanged.

This problem "only" appears on the GUI of JIRA, admin, issue filters, etc.

Thanks!

Accepted answers

All comments

Nic Brough -Adaptavist-

Sounds like someone has set up a "translation" of some sort.

I'd check the admin audit log to see if someone is messing with the issue type definitions, but also, work through exact cases - where is it displaying correctly and incorrectly? Is it by user?

Pascal Rieux

Hi Nic,

Thanks for your quick answer. Nothing (no action from another admin) is shown in admin logs plus when trying to manually set the "Bug" issue type to "Customer Bug" it leads to an error (and I have full admin rights). Not to say it seems to be impossible as an admin.

When such an issue happens, it impacts filters or searches of all users (searching for "issuetype=Bug" leads to 0 issue), but displaying a single issue is ok (the correct issue type is shown)

Pascal

Nic Brough -Adaptavist-

So you're saying something is renaming the issue type? Not translating it or mapping it, but physically changing it?

What's the error when you are trying to rename Bug to customer bug?

Pascal Rieux

Right, no translation or mapping, it looks like a simple renaming. When I try to replay a similar change through the GUI (authenticated as an admin), I reach the following error message:

An issue type with this name already exists.

Nic Brough -Adaptavist-

Ok, so you already have something called "customer bug". Can you try a rename to "freds bug" or something different?

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration