Why do start and due dates defined in a timeline disappear?

[Dennis Zelle]

Hi there!

I've noticed a strange behavior when defining start and due dates of tasks in the timeline view of Jira Work Management.

I've set the start date of a task and its duration directly in the timeline view. However, despite the dates are shown correctly in the timeline, it seems to me that they won't be linked to the task. The dates are not always shown in the task dialog (it's puzzling: sometimes they do, often they don't).

Also, when changing the project view from timeline to another view, e.g., to the list view, the defined start and due dates simply disappear from all views.

Any recommendations how to avoid this behavior? It's quite frustrating that the defined course of a project simply disappears.

Any help is highly appreciated. Thank you!

Dennis

[Boris Georgiev [Appfire]]

Here's an article which describes how to fix the collation https://confluence.atlassian.com/jirakb/how-to-fix-the-collation-of-a-microsoft-sql-server-jira-database-776646810.html

[lorenze larot]

Thanks for the Response @Boris Georgiev [Botron]. Does this KB still applies even if running the query below does not return any result?

SELECT object_name(object_id) as TableName, name as ColumnName, collation_name
FROM sys.columns
WHERE collation_name <> 'SQL_Latin1_General_CP437_CI_AI'
AND object_name(object_id) NOT LIKE 'sys%'
AND object_name(object_id) NOT LIKE 'queue%'
AND object_name(object_id) NOT LIKE 'file%'
AND object_name(object_id) NOT LIKE 'spt%'
AND object_name(object_id) NOT LIKE 'MSrep%'

Thanks,

Lorenze

[Boris Georgiev [Appfire]]

are you still seeing the errors in the log or through the health check UI ?

[lorenze larot]

My bad, Its actually returning result, I had it run against another DB.  Another quick question, I'm not sure if this is possible though.

I'm planning to create a new DB base on this KB. https://confluence.atlassian.com/jira/connecting-jira-to-sql-server-2012-610763188.html.  

-Create an xml backup of our system. 

-clone the existing server and reconfigure the DB connection to point to the new DB.

-do an import from the xml back.up.

Do you think this plan will work? Sorry for asking too much.

Thanks,

Lorenze

[Boris Georgiev [Appfire]]

This should work - yes. Just make sure your JIRA instance has enough RAM because if you're importing large backup it might fail with out of memory if your heap is low.

I've imported ~10GB XML backups and everything is fine with the proper memory settings.

https://confluence.atlassian.com/jira/increasing-jira-memory-5896.html

FIRST test the procedure on a test/staging server before doing this on production!