Projects in projects

HughesTooling · ‎03-05-2015

Is there going to be a way to create projects inside other projects or folders. What I would like is to have a top level folder then folders for customers then projects in those folders. As far as I can tell at the moment all projects go at the top level and it all gets a bit chaotic after a few jobs.

Mark

Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

Roman_Vesely · ‎03-05-2015

Hi Mark,

current design supports Projects only at first level. But inside the Project you can have Folders and subfolders. It's only up to you how many levels you need to create.

Projects are very special at lest from the perspective, that isn't possible to Delete them. You can use only Rename or Deactivate.

But with Folders (subfolders) you can do all operations.... Copy / Move / Rename / Delete

Regards

Roman

Fusion QA team

Roman Vesely

Inventor - Principal QA Engineer

HughesTooling · ‎03-05-2015

The problem is you can do more with projects than folders. For example I don't think you can share a folder and you don't have the project settings. I just looked at the properties for the folder where I store files on my computer and it has 700 folders and 8000 files I'd don't think that's going to work too well the way A360 works now. I don't think only having project at the top level is going to work for anyone doing real work for very long.

Mark

Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

Roman_Vesely · ‎03-05-2015

Thank you for your feedbak.

You are right, Share / Invite works only for Projects.

Thank you for following up with us on this. It's a good idea.

Please, could you share your idea on Fusion 360 IdeaStation: Request a Feature or Enhancement page ?

Regards

Roman

Roman Vesely

Inventor - Principal QA Engineer

kb9ydn · ‎03-05-2015

I (too) think we need to be able to put projects into folders. Most people only work on a few projects at a time, so having them at the top level is ok. But after they are finished, you really want them to go somewhere else where they aren't cluttering up the interface.

Projects inside of projects I don't think would really work.

C|

Anonymous · ‎03-05-2015

Let's say I have a public project (like e-NABLE) that I want to invite lots of people to, but I want it so certain files can only be edited by a core group within the project, is that possible?

HughesTooling · ‎03-05-2015

@kb9ydn wrote:

Projects inside of projects I don't think would really work.

C|

At the moment you have to have projects at the top level. I don't see that as a problem, for example you could have a top level project "Work" then have sub projects and/or folder for all your customers and then your customer projects.

Mark.

Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

daniel_lyall · ‎03-05-2015

that makes sences, the whole thing at top level then diffrent sizes the cut lay outs all in one folder.

it would make life easyer to have a part you make for diffrent people with slight diffrences between each version includeing the cut files all in one.

so template (the part), diffrent versions, cut files. big file yes but only one

kb9ydn · ‎03-05-2015

@HughesTooling wrote:

@kb9ydn wrote:

Projects inside of projects I don't think would really work.

C|
At the moment you have to have projects at the top level. I don't see that as a problem, for example you could have a top level project "Work" then have sub projects and/or folder for all your customers and then your customer projects.

Mark.

But with projects inside of projects you potentially have conflicting access rights. If I want to give someone access to a sub-project of a project, do I have to also give them access to the main project? And how many levels deep could this go? I can see a potential administrative nightmare here.

If what you're looking for is just a simple organization method, allowing folders at the top level with projects inside them makes more sense. And speaking for myself, I wouldn't even use projects at all if I didn't have to. I have no need for all of the extra stuff that comes along with projects; at least not right now. Maybe someday in the future I might need them, but for now they're mostly useless overhead.

C|

julesbpersonal · ‎03-06-2015

Hello Everyone,

This is a very interesting discussion for me (I am a design architect working on Data and Collaboration) and I'd like to understand more about what your needs are.

I would really appreciate it if you could send me an email (jules.brenner@autodesk.com) and let me know what your needs are. I know that some people are sensitve about posting their data on forums, so I'm suggesting an email. Your communications with me will be kept confidential, so if you want to send screen captures of folder organization, that would also be useful. But all feedback will be useful.

It will especially help if you could describe the following:

1.) What your current organizational structure is in your file system (if you use one) or the logical structure of what you use. I am also interested in what you would like to use in future if you don't already do this today.

e.g.

Folder A

- Company X

- Project 1

- Project 2

- Company Y

- Project 100

- Project 200

2.) What you would desire in terms of sharing and controlling permissions. I suggest that you use your organizational structure to comment on this.

e.g. I want to limit one group of designers to be able to work only on Project 100, but want certain people to be able to work on both Company's projects.

While I'm suggesting how you communicate in this way, I'll gladly take whatever information you can give, at whatever levely you prefer to communicate, of course.

Looking forward to hearing from you,

Jules

UX Architect, Data and Collaboration

Jules Brenner

Anonymous · ‎03-06-2015

Workgroup
> Project
>>Folder

Each has it's own permissions that are inherited from the previous hierarchical step unless otherwise specified.

Example:

e-NABLE

>Raptor Reloaded

>>revA Assets

>>>*Raptor Reloaded A v89.f3d

>>>*Raptor A - finger.f3d

>>>*Raptor A - palm.f3d

>>revB Assets

>>revC Assets Under Review

Vibro Labs

>*Vibro Classic v9.f3d

>Vibro Limiteds

>>Vibro Limited 001 v3.f3d

>>Vibro Limited 002 v7.f3d

>>Vibro Limited 003 v4.f3d

>Product Sandbox

>>Foxworth

kb9ydn · ‎03-07-2015

Generally the way I use folders is something like this:

Personal Work

-vehicles

-house

-whatever

Shop Work

-Company 1

--2012

---Project A

---Project B

--2013

---Project C

-Company 2

--2013

--2014

--Project D

--Project E

--Project F

I also have an Archive folder for companies that we've done work for in the past but don't expect to be working for in the future (for one reason or another).

Most of the project specific tools aren't of any use to me (for now) because I use Fusion for machining only, and I'm the only machinist so collaboration doesn't apply.

C|

HughesTooling · ‎03-08-2015

Some info on how I'd like to arrange Projects and Folders.

LEVEL 1.
At the top level I don't mind if I have a folder or project.

LEVEL 2
At the next level I'd like Projects, at this level I'd have a project for each customer. Project at this level would be nicer than folder as you can add company logos and contact details ect.

LEVEL 3
I have three types of customer. First customers that only work on their own projects, so I'd like to have projects at this level. Second Customers that only work for their customers, again I like projects so I can have logos and other details for their customers. Third are customer that have their own projects and project for their customers.

LEVEL 4
I'd like more projects for my second and third type customer projects.

Looking at the above I'd be happy with just projects and no folders at all. As for sharing, if you share a project with someone they'd only have access to the project at that level and down, no access to project above that level.

Temp Uploads
-Quotes
-Imports

Library
-Parts

Work
-Company A
--Project1
--Project2
-Company B
--Company B Customer 1
---Customer 1 Project 1
---Customer 1 Project 2
-Company C
--Project1
--Project2
--Company C Customer 1
---Customer 1 Project 1
---Customer 1 Project 2

Thanks Mark.

Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

julesbpersonal · ‎03-10-2015

Thanks Luke - this is useful feedback.

Jules Brenner

julesbpersonal · ‎03-10-2015

Thanks for taking the time - I appreciate it. I personally like the idea of an Archive of sorts.

Jules Brenner

julesbpersonal · ‎03-10-2015

Again, thanks Mark - I value the time you take to write this up. It really helps to understand customer needs, and for us to make good design decisions for the software.

Jules Brenner

Anonymous · ‎03-10-2015

I suspect that it need not be complicated. If you just have folders that the owner can set permissions (read, write, delete), just about any scenario or case would work. The problem right now is you can only invite people to projects and you have no way to control what happens after that.

Fusion