Showing results for 
Search instead for 
Did you mean: 
Showing results for 
Search instead for 
Did you mean: 

Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X

Previous revision in release target change task

Previous revision in release target change task


we are often facing situation when via change task releasing dozens of objects but not all of them having the same LC state. I mean situation when all objects been revised to "In work" state but:

30 objects have release target "State 2"

50 objects have release target "State 3"

10 objects have release target "State 4"

40 objects have release target "State 5"

It is very complicated and time-consuming to sort out all objects in change task and set up proper state for each group of objects. We would like to have an option "Previous revision".



This function will automatically set up the same state like it was in previous revision. It would work like in a case when object has been revised from "State 3" => "In work" so function will set up again "State 3".



Using this option when all objects preselected can send them back to the same states without manual selecting.

23-Emerald II

Why do you have multiple release states?

What am I missing in this request?

All of our drawings go to a single state of Released from a working state of pre-release for numeric revision designs. (For alpha, the designs go from Design state to Prototype state.)

We have a total of 6 states in the LC, but the rules limit where a promotion can take a design to based on revision. When we do a promotion request, they designers are only offered 1 state to release their design to.



Our LC states represents manufacturing process. We work like this:

- imagine have a product (final ASM) containing 90 pcs

- 30 pcs are in state 1 (prototype 1) + 30 pcs are in state 2 (prototype 2) + 30 pcs are in state 3 (serie)

- revise all of them to "in work" and modify (checkout/in)

Now comes the pain:

- sort out all 90 objects in change task in order to set them into the same (previous) release state = back to P1/P2/Serie

PS: All objects in resulting objects table are "in work" so you have to find out what was previous state for each object (looking into affected objects table to see previous revision state)

New option "Previous revision" can set the same (proper) state by 1 click instead of digging which state was the former one...

Community Manager
Status changed to: Archived


We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.