Clone button missing in Project Settings page

Legacy Modelling
1

For some strange reason, the “clone” button is not available anymore for projects, even for full admins with no restrictions.
It was working OK just a week ago, but now it just dissapeared.

We are using version 3.7.6

2

Some more info about the error. Using Chrome Developer tools I can see the button has been disabled using CSS:

Clone

Clone this project to reuse its deployment process and variables.

    <a class="btn btn-info" href="#/projects/new?clone=Projects-342&amp;grpid=ProjectGroups-282">Clone</a>
  </div>

In the console tab I can see this error message:

TypeError: Cannot read property ‘list’ of undefined
at Object.fn (octopus.min.js?v=ac1f6990-c190-11e6-af49-bf3cf2237575:164)
at Scope.$digest (octopus.min.js?v=ac1f6990-c190-11e6-af49-bf3cf2237575:21)
at Scope.$apply (octopus.min.js?v=ac1f6990-c190-11e6-af49-bf3cf2237575:21)
at octopus.min.js?v=ac1f6990-c190-11e6-af49-bf3cf2237575:159
at Object.success (octopus.min.js?v=ac1f6990-c190-11e6-af49-bf3cf2237575:157)
at XMLHttpRequest.request.onreadystatechange (octopus.min.js?v=ac1f6990-c190-11e6-af49-bf3cf2237575:155)

3

Hi Jose,

Thanks for getting in touch! I’ve tried to replicate your problem with Octopus 3.11.10 but I couldn’t and the clone button was available to me.

We’ve fixed quite a few JavaScript problems recently so you might be able to resolve your problem by upgrading to the latest version of Octopus.

That being said. I was able to reproduce the JavaScript problem you’ve reported and and a fix for it will be released soon. I created an issue so you can track progress of our work.

Please, let me know how you go.

Regards,

Pawel

4

Hi Jose,

There was a similar problem reported today where one of our customers was a member of two different teams assigned to. different project groups. Can you check whether this also applies to you?

Regards,

Pawel

5

Hi Pawel

thank you very much for your reply.

For the time being, we have the workaround of getting the url to the clone page using Chrome developer tools. The problem is data dependent, because the cloning was working OK just a few days ago with this same version.

When there is a version that definitely fixes the problem, we will upgrade.

Regards

Jose

6

Hi Jose,

That makes sense. The JS fix will be released as part of 3.11.11.

Regards,

Pawel

7

Hi Jose

Just to let you know I’ve tracked down the issue, and I’m hoping to have a release out in the next day or so.

Hope that helps.

Regards,
Matt