we work with many branches and most often i would like to create various snapshots of the graph. other then the default history timeline. thank you.

needed to rename my org on my cloud account, and it was a process. The website should warn you like on github for some people that have no clue what they are doing. Also this should notify all plastic instances about the change similiar to update repo or branch notification. Also this should be able to switch the logical phyiscal file directory. i ended up having to check everything out in a workspace and all of that jazz.

it would be rad to be able to click and drag a line between the from and to nodes to start a merge. Display window if conflicts.

it would be nice to be able to click one of these menu item icons to open up a window to enter this info in. I think this will help iterate on user feedback.

Hi, our company switched from Slack to MS Teams, but unfortunately, the plastic cloud trigger function does not seem to be properly supported at MS Teams.

MS Teams is also a program with as many users as Slack. We hope that MS Teams will be supported through MS Teams's 'Incoming Webhook' connector, just as you have supported Slack and Discord.

We think it will be easy for you. However, I think the benefits will be great for companies using MS Teams. I hope you will consider this positively.

Be able to split tabs and dock them into different areas of screen within a workspace in windows GUI. For example, 50/50 vertical split showing branch explorer and pending changes.

Dark mode is especially popular among devs, this would be a great QoL feature to have.

Stop spamming this stuff every single day and in every tab, every single new version.
The tick DOESNT DO ANYTHING.
Please fix it, annoying as hell.

Cuando hay una nueva versión de Plastic, el banner del búho tapa la lista de repositorios y no puede accederse a los que oculta, dificultando el trabajo. Lleva meses siendo así, y no siempre se tiene el tiempo para detener el trabajo que estás haciendo y priorizar la actualización del cliente de escritorio sólo para poder acceder a tus workspaces.

Cuando hay una nueva versión de Plastic, el banner del búho tapa la lista de repositorios y no puede accederse a los que oculta, dificultando el trabajo. Lleva meses siendo así, y no siempre se tiene el tiempo para detener el trabajo que estás haciendo y priorizar la actualización del cliente de escritorio sólo para poder acceder a tus workspaces.

Even though I have "Disable All Tips" checked, the "A new version is available" tips are constantly taking up the bottom half of screen because of new versions. I would like to disable the tip showing, you could notify us of new versions somewhere that is not so obstructive. If it is important that we stay up to date with the latest versions, then there should be a background downloader and installer to keep us up to date but the constant nag message taking up the bottom half of screen is too much.

ignore.conf (and similar files) don't understand all nouances of git glob notation, even though that's a worldwide de-facto standard.

Even Unity itself, and tools like Fmod for Unity, will provide or add ignore.conf entries that actually don't work in Plastic, but should, such as:

# Ignore the Cache-file since it is updated locally either way
/[Aa]ssets/**/FMODStudioCache.asset
/[Aa]ssets/**/FMODStudioCache.asset.meta
/[Aa]ssets/Plugins/FMOD/Cache.meta
/[Aa]ssets/Plugins/FMOD/Cache/Editor.meta

ignore.conf, if automatically re-written by the gui (e.g. by right clicking and adding an item to it) will lose all its existing comments, formatting, etc.

This is inacceptable and makes ignore.confs extremely hard to maintain, especially in Unity projects.

We are using the Jenkins pipeline plugin and we would like to have the option to create a dynamic workspace instead of a normal one.

It's easy to forget to merge a branch after a code-review is completed.
Change the colour-coding:
- Blue: Review requested
- Red: Rework requested
- Yellow: Reviewed
- Green: Merged

Alternatively you could add separate triggers for this purpose.

Teams that use a replication workflow currently have at disposal only these triggers:

before-replicationwrite
after-replicationwrite

before-replicationread
after-replicationread

They are however lacking any details about what was introduced in the replication.

If you use them to connect for example with Discord, you will repeatedly receive "Replication write operation on myrepo" notifications that lack any details.

Possibility to set "Update and Checkin operations set files as read-only" per repository rather than globally would make easier for Artists that use different repositories for raw and cooked data assets to work with third party tools like Maya, etc.