Issue Type Scheme changed to default

[Scott Murphy]

Hi,

We have a template Issue Type Scheme which is used on the vast majority of our projects (around 700). The projects are created via the Delegated Project Creator application.

Twice in the past few days, most of our projects have randomly reverted to the "Default Issue Type Scheme", which is assigned to "Global (all unconfigured projects)".  We reverted them all back in bulk, but its just happened again. This means our new issues have more issue types available than they should which is causing headaches with users.

We cannot pinpoint what is triggering this to happen, and we've made no substantial changes to our system.  It has never happened in the 5+ years we've been using this template. We did upgrade a handful of applications recently which seems to coincide, being: 

- Atlassian Troubleshooting and Support Tools (com.atlassian.troubleshooting.plugin-jira version 1.47.1)
- The Scheduler (pl.com.tt.jira.plugin.theschedulerpro version 6.5.7)
- Smart Checklist (rw-smart-checklist-biz version 6.5.1)
- Delegated Project Creator for JIRA (com.wittified.jira.project-creator version 4.8.7)
- Jira Cloud Migration Assistant (com.atlassian.jira.migration.jira-migration-plugin version 1.9.4)
- Links Hierarchy (com.docminer.jira.issue-links version 7.4.1)
- Excel-like Issue Editor for Jira (jp.ricksoft.plugins.excel4jira version 1.21.4.0)
- Email This Issue Server (com.metainf.jira.plugin.emailissue version 9.5.0-GA)

Has anyone experienced anything like this before or can give a clue to where I might find out? Have had a look at logs but haven't spotted anything.

Thanks!

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

Jira does not have any functionality that could do this, so it's either

• A human doing it via the UI or database manipulation (SQL access should never be allowed)
• A human writing a script to do it
• An app written to do it, either deliberately or as a bug

The third of those sounds most likely to me, as the timing of the app upgrades seems suspiciously close to when it happens.

First thing to do is check the admin audit log - it will record most of those possibilities.

Then look hard at your apps.  I would rule out 

• Atlassian Troubleshooting and Support Tools
• Smart Checklist
  
• Jira Cloud Migration Assistant
• Links Hierarchy 
• Excel-like Issue Editor for Jira 
• Email This Issue Server 

as they don't have any need to be amending project scheme settings, and hence have no code to do so.

I'd look at 

• The Scheduler (but only if you've used it to schedule admin checks and corrections)
  
• Delegated Project Creator for JIRA (although this still needs a human to tell it to make changes)
  

[Scott Murphy]

Thanks Nic. After more experimentation we did narrow this down to project creation being the trigger, and then Delegated Project Creator being the natural suspect.

They confirmed over email that this is a known issue in their latest release and they are working on a fix.

Many thanks for your help,

Scott

[Gabriel Udvar]

Hi @Scott Murphy ,

I think we're being hit with the same issue. Can you tell me how you managed to test this and isolate the issue and most importantly, how you managed to recover from this?

Unfortunately, I have quite a large Jira instance and I've got about 3800 projects affected by this :| 

Thanks!

Gabriel

[Scott Murphy]

Hi Gabriel,

If you're issue is caused by Delegated Project Creator, like ours, then they released v5.0.0 today which purports to fix it.

Re setting everything back, we have done that under Issue Type Scheme by 'Allocating' it it in bulk to multiple projects.

Fortunately for us, 95% of projects are on one type so it's feasible to manually select the appropriate ones (albeit a bit tedious)