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.

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.

Add a way to know the keyboard shortcut of a specific action by displaying it in a tooltip or contextual menu.

This will greatly help new users to improve their workflow, without having to read a doc that list shortcuts.

There isn't anything on the AUR from the Community for Plastic and I would like to use Plastic SCM on my Arch based PC. Could you make it available on there?
I can only use the one in Unity but it is buggy and I think it doesn't have branch support... Or another alternative that Unity is using too is AppImages!

Pretty self explanatory. As it stands right now, a repository is completely secure permissions wise until a new branch is made, which may expose that data to people who shouldn't have access.

I often find myself waiting for a teammate to finish with a file lock. It would be great if I could subscribe to a notification for the next time the file is no longer locked so I can sync it and begin my own work.

When merging from one branch to another, in the Differences window, the only labels are "source", "destination" and the changeset for each. It would be much more helpful if it listed the branch as well, as it is sometimes easy to forget which was the source and which was the dest. Plus it serves as a google safety catch in case you merged the wrong direction.