Matt Doar_tzgiej Community Champion

Perhaps use Project Categories?

What's the difference between a buffalo and a bison? You can't wash your hands in a buffalo. (think Aussie)

I've seen it work with the DB on the same machine, though that is only recommended for smaller Jira instances. You'd need to check that the restored snapshot can still access its local DB and no other DB though. Stopping email getting read could be done by disabling all mail habndlers before taking a snapshot, but that's…

When you restore a snapshot, make sure it is not reading email from mailboxes used by production Jira. Also make sure it is accessing a snapshot of the DB, not live prod DB on another server

I don't think that can be done via the UI. Source code change probably

Good info, Nic. And let's not raise the whole case sensitive or insensitive kettle of fish!

Stop Jira, remove files in that directory. But it's not common to have problems there. Make sure you have enough space in /opt too. 

If the custom field is locked, I wouldn't change it. Based on past experience of using the JIRA Agile plugin and the JIRA Service Desk plugin. Can you disable the Jira Mobile Connect plugin?

I'd suggest renaming your UUID custom field.

And, is it so?

I suggest you disable all Chrome extensions and test again. Then reenable one by one. AdBlock caused me problems a few weeks ago, so I whitelisted my domain to fix that

It may be that when you edit the Confluence page, the jiraissue macro which is what provides the table of Jira issues connects to Jira to refresh its data. So you see the changes that have been made in Jira. I don't think that Confluence is going to Jira and updating the Jira issues though.

Nothing obvious jumps out at me, except all the String comparisons in the case statements. I'd start simple and see how that runs. For example, how long does a script take that just calls setSummary with a fixed string. Then add more code. Perhaps use a StringBuilder class instead of concatenating Strings? In the end, some…

Cos my telepathy bill is huge this month

Can you post the guts of the script?

Which database are you using? It may be that the datetime is not being shown in full, even though it is in the db

Not often I beat you to a post :) Good to know the DB schema hasn't changed there. 

A single changegroup can have multiple changeitems in it. I see a datetime field named created in changegroup with Jira 7.2.10 and MySQL I see datetime in the data: mysql> SELECT changeitem.oldstring, changeitem.newstring, changegroup.issueid, changegroup.created -> FROM changeitem -> JOIN changegroup ON…

https://community.atlassian.com/t5/Jira-questions/Official-Atlassian-support-for-JIRA-on-Docker/qaq-p/568641 has some useful comments about docker Oracle is a supported database but check for your Jira version at https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html

Do you have a custom URL field on your create screen. and are adding long URLs to it?

1. See if the mail queue is getting mail items 2. Check your JVM command line flags are not disabling email

You can sort by lables in the Issue Navigator page. But consider what happens when there are multiple labels on some issues.

In 7.2 it's not in the history tab of an issue, so I'm not sure it is recorded in ChangeItem. The old project keys are recorded in the project_key database table though

https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/?_ga=2.154279934.791995671.1520270742-100297201.1518149632#api/2/permissionscheme-deletePermissionSchemeEntity I think, Get permission scheme grants then iterate to find the one you want and then use Delete permission scheme entity

Though it is worth looking at the linked issue in https://community.atlassian.com/t5/Jira-questions/Jira-database-schema-change-for-customfieldvalue/qaq-p/743828#M241710

Generally its not the amount of data in a Jira database that causes performance problems. More important is the size of the Lucene indexes, particularly the main one (issues). A full reindex should reduce the size of your Lucene issues index if you have used custom field contexts to change the fields in each issue. I don't…

Software and Service Desk are apps, i.e. plugins, for Core. Under the covers

REST or UI, Server or Cloud?

I would start with https://confluence.atlassian.com/jirakb/invalid-column-type-getblob-not-implemented-for-class-oracle-jdbc-driver-t4clongrawaccessor-during-backup-process-854131615.html and if you need more help, contact Atlassian Support

Did work for me either