Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with Project Key after migrating to Windows

daniel_hedberg July 4, 2019

So we migrated our jira installation to Windows from Linux one of our projects had a key CON. The attachments connected in this project was stored in attachements/con directory this is not allowed in Windows its a reserved name so a folder like that cant exist. So it created the folder _CON the problem is that we know cant see old attacments or add new ones we get the error: Could not save attachment to storage: Unable to create target directory

 

Does anyone have any idea i tried to change the project key in Jira but this did not have any effect.

1 answer

1 vote
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 8, 2019

Hi Erik,

Windows has a few different reserved words that cannot be used in the file path:

PRN, AUX, CLOCK$, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, CON, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9

To get around the scenario you ran into on the COM value post migration you will want to do a Bulk move action to rename the project key on the source data so that both the pkey and project data folder containing the attachments are updated, before migrating so you can align the old path/new path.

If you just rename the pkey the file path will hold on to the CON naming convention, but if you move the issues to a new project the attachments are moved to the new projects folder structure as well.

So the process to follow will be:

  • Create a new project with matching configurations and a non reserved Pkey something like 'CONEXE'
  • do a Bulk Move operation to move all the issues from CON to CONEXE
  • Delete the empty CON project
  • Migrate to the new server

An additional note is that the bulk operations can return a maximum of 1000 results by default to prevent degrading system performance.  You can increase the limit as described here or restrict the search to do it in batches of 1000 issues at a time.

Regards,
Earl

Suggest an answer

Log in or Sign up to answer