Give users control of versioning and revisions

[Anonymous]

It would be ideal to be able to decide the version. In Creo, there are iterations that occur during check-in (counterpart to "save" in fusion. This means that versioning of a component  is expressed as #.#

Therefore when I save "component V 0.0" the new version would be "componentV 0.1". 

Version is "0.1" 

Revision is "0"

iteration is ".1 of revision 0" (1st iteration of v0)

When I choose to make a new release of a component/assembly, I want to be able to revise the component. Therefore the requested "revise" command would create a new milestone version (or a release) that can be communicated down into the PLM and ERP systems for logical chronological version numbering.

Why is this needed in my opinion?

Iterations keep track of all saves.. this is important for the current brilliant system that can separate all saved instances... however, lack of iterations of version (the ".1" in "0.1" )it makes it difficult to refer to a particular approved version.. this is especially confusing when communication with suppliers. For instance, fixing a particular version based on suppler feedback will result a new version, not an iteration.

To solve for the synchronization to drawings, I suggest that drawings will be embedded in the component.. the way a flat pattern is currently implemented. Parameters would also be shared.. and drawings would be copied with parts... but that's a separate idea, so I'll post it separately.

[ruedi.weber]

This would be a very welcome addition to me too. It would be also very nice, to have a document event in the api to be notify about the change of a version.

This would allow us to realise a technical seamlessly interfacing workflow to maybe slicing software or other post processing systems to beside ERP systems.

[Anonymous]

This is a great idea. Having a deliberate version change at a significant milestone with incremental changes between makes a lot more sense than a series of otherwise undifferentiated version numbers. This way will be intuitive to people not involved with the design, whereas the current system is confusing.

Version 1 as the prototype, V2 the next run then V3 the production part is a lot more intuitive than version 8 the prototype, version 31 the test and version 48 the production version, which will then wind up being version 53 after a few iterations of the drawings.

[Anonymous]

This was a use-case for one of our departments which have been reluctant to use the tool as they are using the iterations to track less important changes than a full version change - also many of our suppliers utilize this versioning technique.  We also would like to see the ability to use A.1, A.2, A.3 in production (design phase uses numbers, production uses letters) for interim changes not demanding a full new revision.

[jeremy_lambert]

Hi all,

We've been working on some capabilities in this area and have more on tap. The first step in this process is something we have been calling 'Milestones,' essentially a way to tag or mark a change as significant or noteworthy. We're at a point where we are looking for some customers to test this out and give us feedback. If you're interested, please private message me.

Thanks,
Jeremy

[Anonymous]

Thanks for implementing the milestone system @jeremy_lambert . We have been working with this feature, however, it is an incremental improvement that has not helped us with version tagging outside of Fusion 360. Milestones are not visible to other stakeholders in the project, or other collaborators who are not using Fusion 360... unless we annotate them manually into drawings or file names... actions that can be done without the milestone feature.

Perhaps I have not understood how to properly use the milestone feature? Tips are welcome if that is the case.

I am still hoping you would consider implementing feature(s) that support the workflows described in the idea and in the comments by other users. Thank you all for supporting this development suggestion!

[TimeraAutodesk]

Hi All,

We are beginning to work on how the first wave of release and revision management support in Drawings will function and feel like, so I wanted to follow up on this thread with the good news! If you would like to see more details, and be a part of providing early feedback, please see this post on the Feedback Hub.

Best,

Timera