Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Ability to unwittingly interfere with a pending release
shawn_crocker
Member, OS Professional Posts: 869 PRO
in General
I'm just putting this out there to see if this is a worth candidate for an improvement request or if this is a bug. I am finding it undesirable that an individual can accidentally interfere with the progress of another pending release. If a person creates a release and one of the part numbers in the release is in another pending release, the candidate warns them of this. We have an enterprise setting enabled that stops the release from being submitted under this condition. The concern for me is that there is nothing stopping the individual from just changing the part number in their new release and then proceeding.
When this happens, the other pending release will not allow transitioning to a released state. The pending release will also not let the user know anything is wrong. An approver can release the candidate and everything will seem fine. Except the release just doesn't actually go through. The only way to find out why the release will not go through is to dig through the JSON log of the release. I'm also thinking the release candidate should provide a more user friendly, less JAVA scripty way for a none tech savvy individual to get to the bottom of why there release continues to remain in a pending state even after releasing.
When this happens, the other pending release will not allow transitioning to a released state. The pending release will also not let the user know anything is wrong. An approver can release the candidate and everything will seem fine. Except the release just doesn't actually go through. The only way to find out why the release will not go through is to dig through the JSON log of the release. I'm also thinking the release candidate should provide a more user friendly, less JAVA scripty way for a none tech savvy individual to get to the bottom of why there release continues to remain in a pending state even after releasing.
Tagged:
0