Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

(thinking…)

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

531 results found

  1. Export csv or md of selection of changesets or specific branch

    when generating md files for a list of changes, have to do this manually with copy paste, it would be nice to select a set of changesets and have it automagically export to a spreadsheet

    1 vote
    0 comments  ·  Admin →
    How important is this to you?

  2. ability to rearrange nodes in the graph tab

    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.

    1 vote
    0 comments  ·  Admin →
    How important is this to you?

  3. make it easier to rename your organization within the software.

    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.

    1 vote
    0 comments  ·  Admin →
    How important is this to you?

  4. be able to merge branches visually on graph tab

    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.

    1 vote
    0 comments  ·  Admin →
    How important is this to you?

  5. Make PlasticSCM Support more than 1000 users when using Active Directory authentifaciton

    Default Active Directory limit request result entries to 1000 entries. So when you have more than 1000 users in your Active Directory database, the "select group or user" popup window will fail retrieve the list of user and group.

    It is not always possible to increase the limit for request because IT responsibility is sometimes far from people responsible for PlasticSCM server. Also changing the query limitation on Active Directory has an impact on the entire company infrastructure and it is a huge risk.

    I have read Active Directory query can use "page search" to split request result (see link…

    4 votes
    1 comment  ·  Admin →
    How important is this to you?

  6. Make the "Disable all notifications" button actually DISABLE ALL NOTIFICATIONS.

    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.

    5 votes
    1 comment  ·  Admin →
    How important is this to you?

  7. Visually indicate, in Code Reviews, reviews that have been merged into main

    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

    7 votes
    1 comment  ·  Admin →
    How important is this to you?

  8. miguel.valles@psious.com

    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.

    3 votes
    1 comment  ·  Admin →
    How important is this to you?

  9. Keep Comments in ignore.conf

    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.

    1 vote
    1 comment  ·  Admin →
    How important is this to you?

  10. Jenkins Dynamic Workspace support

    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.

    1 vote
    1 comment  ·  Admin →
    How important is this to you?

  11. Display shortctus in the UI

    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.

    4 votes
    0 comments  ·  Admin →
    How important is this to you?

  12. miguel.valles@psious.com

    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.

    3 votes
    0 comments  ·  Admin →
    How important is this to you?

  13. Parity with .gitignore Syntax

    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
    1 vote
    0 comments  ·  Admin →
    How important is this to you?

  14. Fire the checkin triggers for each new checkin introduced with a replication

    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.

    3 votes
    0 comments  ·  Admin →
    How important is this to you?

  15. Possibility to set read-only on update/checkin per repository rather than globally

    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.

    1 vote
    0 comments  ·  Admin →
    How important is this to you?

  16. Have separate permissions for repository read / view access

    This would reduce the amount of manual permissions work massively, as I feel I am battling the hierarchical system all of the time to allow things to be enabled properly.

    An example of this is when I'm trying to give access to just one branch.

    At the moment, giving the repository read / view access (which is required for setting up the repository) then enables that read / view permission for every branch. I then need to manually go through each branch, disable the read and view access and repeat.

    This persists down to the folders also, where we need…

    6 votes
    0 comments  ·  Admin →
    How important is this to you?

  17. Create Zoho Sprints Integration

    1 vote
    0 comments  ·  Admin →
    How important is this to you?

  18. Enable branches to inherit permissions from parent branches

    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.

    3 votes
    0 comments  ·  Admin →
    How important is this to you?

  19. Mac - Tree View in Pending Changes

    4 votes
    0 comments  ·  Admin →
    How important is this to you?

  20. add a "notify me when unlocked" option for locked files

    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.

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
1 2 4 6 … 26 27
  • Don't see your idea?