New tickets in dashboard is wrong after upgrade

[montoxic]

Hi

I have just upgraded otrs 3.2.8 to 3.3.1.

The upgrade went fine, no db errors and everything is working except the new tickets module in dashboard.
i have no custom configuration of the dashboard.

Have anyone any idea what is causing this. The log files does not saying anything?

The thing i can se is that some columns are missing in "available columns" like age and stuff like that. In sysconfig i can se all columns and they are enabled.

Se my 2 pictures.

otrs_dashboard.png

avaiblecolumns_newtickets.png

[yuri0001]

You need to drag Column Names from Availablbe columns frame to Visible columns and drop them there. Then save configuration.
And another. Some columns will mandatory for some widgets, so they not represent in Available columns.

[sky8000]

Hi,

I have the same problem. Some of the columns are just not available in the customization even when active by default on sysconfig.
In my case I upgraded from OTRS 3.2.11 to 3.3.1.

There were some warnings about foreign key constraints when I ran the database upgrade script but everything else seems to be working fine.

[yuri0001]

SysConfig in Ticket -> Frontend::Agent::Dashboard => DefaultColumns for all widgets have a name of field and a digit which control mandatory of it.
If - 1 -this field you will see in list of available columns, if - 2 it is mandatory and you will see it in list of Visible columns. You can add a field/column such Created and give him 2 and give 1 for Age.
Mind - TicketOverviewSmallPageShown must be active

[sky8000]

Hi again,

Although all fields are configured in Ticket -> Frontend::Agent::Dashboard => DefaultColumns with the flag set to 1 or 2 they don't show up in pending reminder or open ticket widget (please view attached screenshots).

For some reason I do not know the New Ticket widget is working properly.

[crythias]

It seems (just a guess) that the items that aren't appearing don't have a 1

[sky8000]

Hi,

All flag settings are set to 1 or 2. I double-checked the configuration. The problem must of another nature.
Just check both the screenshots from my last post.

[crythias]

2!=1

[sky8000]

Come on. I know that.
As far as I know from a post here in this thread 1 means that the field is available (for the user to add) 2 means that is mandatory.

The problem is that the fields that are set to 1 don't show up in two widgets. We've played with these settings to see if something changed but in two widgets nothing happens.

In the "New Tickets" widget changes on these settings have the desired effect.

[crythias]

how would 2 be mandatory in a list?

[sky8000]

Hi,

Just solved the problem. There was one small step I missed in the upgrade instructions that was running the migration script below (Upgrade Step 9, Schema update on http://doc.otrs.org/3.3/en/html/upgrading.html)

Code: Select all

shell> scripts/DBUpdate-to-3.3.pl

After I ran this script everything started working.

Thanks everyone.

[sky8000]

how would 2 be mandatory in a list?

If you read an older post from yuri0001 (copy below) you'll understand what I am trying do say.

SysConfig in Ticket -> Frontend::Agent::Dashboard => DefaultColumns for all widgets have a name of field and a digit which control mandatory of it.
If - 1 -this field you will see in list of available columns, if - 2 it is mandatory and you will see it in list of Visible columns. You can add a field/column such Created and give him 2 and give 1 for Age.
Mind - TicketOverviewSmallPageShown must be active

[crythias]

ok. I apologize for misunderstanding.