After a Issues is moved to a different Project, the attachment brings up a 404 error

Question

After moving an issue from one project to another, clicking on it will bring up a 404 error.

I am not the only admin and there may have been recent changes that i am not awere of, but this was working fairly recently. I have asked other admins but we can't figure it out..

Thoughs?

Thanks,

Adam

adam goodwin1 · Answer

Thanks.. yea I was looking at that.. I was not the one who Changed the project key.. so not sure how it was done. Thats what is happening, the attachment folder is keeping the the old project key (GASP) and making folders for newly added attachements, but any attachments on an an issue that get moved in to the porject are using the new key (CM)

thanks.. I will contact Customer Support

Peter Van de Voorde · Answer

Hi Adam,

In this pages it's explained that what you are seeing in the file structure is the normal behaviour : https://confluence.atlassian.com/display/JIRA/Editing+a+Project+Key

The attachment folder will keep the old project key. It's not correct that the links break.

Is GASP the new or the old project key?

And how exactly did you change the project key of that project?

I would advise you to contact Atlassian Support directly here :

https://support.atlassian.com/customer/home

Best regards,

Peter

adam goodwin1 · Answer

So I figured out the root of the problem..

One of the Projects were recently renamed and now when I move an issue to the new project name, it puts the attachemets into an folder named for the old Project..

Any thoughts as to how to fix this?

thanks

Adam