526 results found

1. Unified diff for multiple files

   In SVN there was a great feature that allowed you to select multiple files in your "Local Changed" window and the press "Show unified diff".
   This would compare all the files and show you all the changes in one window.
   It would give you information inbetween the changes to let you know which file you were viewing the changes at.

   This was great when you did a "rename" on a variable on hundreds of files etc. Allowing for quicker code reviews ( that are important at our company ).

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. When managing multiple changelists, allow us to checkin with the changelist's name

   When I'm managing several changelists I give them different names depending on the context. When checking in, I'd like to have the option of using the changelist name as the comment, instead of typing in the comment first and then choosing to check in the changelist.

   e.g. - I might have the following:

   Changelist: "Feature XYZ"
   Changelist: "Spelling error"
   Changelist: "DO NOT CHECKIN"

   I'd like to check in "Feature XYZ" but not "Spelling error" (as it might be irrelevant to the feature changelist). I would like to:

   1. Right click on "Feature XYZ" and select "Checkin Changelist"
   2. A dialog box pops up with the comment field, prepopulated with "Feature XYZ" as the changelist comment.
   3. I alter the comment "Feature XYZ" if I want, or otherwise just click on "Checkin" button on the new dialog and check in.

   .. something like that. Having to enter something into the "main" comment box each time is cumbersome.

   Thanks!

   When I'm managing several changelists I give them different names depending on the context. When checking in, I'd like to have the option of using the changelist name as the comment, instead of typing in the comment first and then choosing to check in the changelist.

   e.g. - I might have the following:

   Changelist: "Feature XYZ"
   Changelist: "Spelling error"
   Changelist: "DO NOT CHECKIN"

   I'd like to check in "Feature XYZ" but not "Spelling error" (as it might be irrelevant to the feature changelist). I would like to:

   1. Right click on "Feature XYZ" and select "Checkin Changelist"
   2. A dialog box pops… more
   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Diff all selected chenged files with CTRL-D

   This is a minor thing but one that bugs me a lot. In P4, when you have multiple files selected in the pending changes view, you have hit ctrl-d to diff all the selected files against the current revision. Plastic has the same feature except it only functions when you have a single file selected.

   I find it very usefull to trigger a diff for multiple changed files so that I can review all changes without having to constantly context switch back to plastic to open the next file. Alternatively I have to manually select each file, hit ctrl-d, which for a largish changelist can take a while.

   This is a minor thing but one that bugs me a lot. In P4, when you have multiple files selected in the pending changes view, you have hit ctrl-d to diff all the selected files against the current revision. Plastic has the same feature except it only functions when you have a single file selected.

   I find it very usefull to trigger a diff for multiple changed files so that I can review all changes without having to constantly context switch back to plastic to open the next file. Alternatively I have to manually select each file, hit ctrl-d, which… more

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Add PLASTIC_REPLICATION_TARGET environment variable to Replication Read triggers

   In a distributed development environment (a central server with the 'good' set of source), when you use Replication to Pull a branch you can identify the source repository in the before-replicationwrite trigger from the PLASTICREPLICATIONSOURCE environment variable and the target repository from the PLASTICBRANCH environment variable. In this way you can check that the repositories match and you aren't corrupting your local repository with branches from another repository.
   However, when you Push a branch, there is no way for the before -replicationread trigger to check you aren't corrupting the central repository by matching you local repository name with your target (central) repository.
   Could you add PLASTICREPLICATION_TARGET with the repository on the target server?

   In a distributed development environment (a central server with the 'good' set of source), when you use Replication to Pull a branch you can identify the source repository in the before-replicationwrite trigger from the PLASTICREPLICATIONSOURCE environment variable and the target repository from the PLASTICBRANCH environment variable. In this way you can check that the repositories match and you aren't corrupting your local repository with branches from another repository.
   However, when you Push a branch, there is no way for the before -replicationread trigger to check you aren't corrupting the central repository by matching you local repository name… more

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Support side-scrolling (Particularly in Branch Explorer)

   Allow users with side-scrolling capability to use it in the Branch Explorer and diff viewer.

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Add support for targa files in Gluon

   If I have a tga file selected in Gluon, I just see the windows file icon for it instead of a preview of the image. Other file types, such as png show a preview of the image when selected.

   Targa is a common file format used for video game textures

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Improve Issue Tracker Support for MonoRepos

   Firstly, we use the Jira integration in plastic so I only have experience in this area. I assume the same concepts apply to other trackers but I can only speak from my experience with Jira

   Recently, we moved from using a number of xlinked repositories to using a MonoRepo in Plastic. It's no surprise that plastic already has good support for the MonoRepo approach.

   One area we have found that is lagging a little behind is the issue tracker integration though.

   Currently, the relationship for the Jira integration in plastic assumes a mapping of 1 to 1 for a repository to a Jira project. In a MonoRepo this becomes problematic because we still track our issues in multiple Jira projects but all of those projects are stored in a single Plastic Repository.

   Here's a few things that I think could be improved
   - Allow a wildcard in the "Prject Key" field when configuring integration for a plastic repository. This would mean that Plastic should find all tasks in all projects for my user rather than in a single project.
   - Provide more options for branch names. This is to do with when you create a new branch from a Jira task. Currently, there's a "Branch Prefix" setting in the integration options. This doesn't apply for a MonoRepo. We in fact do not wish to apply a prefix at all but would prefer to use the entire Jira task key such as MYPROJ-12324. This would mean that the task key may be PROJ-001 or XYZ-002 depending on the Jira project it belongs to. Two options that a user might be able to select for the branch name option might be something in the form of "Use Jira Task Key" OR "Use Jira Task Id with custom prefix"

   Firstly, we use the Jira integration in plastic so I only have experience in this area. I assume the same concepts apply to other trackers but I can only speak from my experience with Jira

   Recently, we moved from using a number of xlinked repositories to using a MonoRepo in Plastic. It's no surprise that plastic already has good support for the MonoRepo approach.

   One area we have found that is lagging a little behind is the issue tracker integration though.

   Currently, the relationship for the Jira integration in plastic assumes a mapping of 1 to 1 for a repository… more

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Add Checkout to the pending changes context menu

   A convenience suggestion. Could we get the checkout option in the context menu for items listed in checkin changes?

   I find that Changed Items tends to reflect the items I want to checkout, so navigating the explore workspace tab becomes cumbersome in comparison.

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Context menu: Merge to this branch/changeset...

   Currently, when I'm on a branch and I want to merge what I have to another branch (e.g. main) I have to right-click on my current branch/changeset, select "merge from this [] to..." and then pick the target from an endless list of all my braches.

   This is incredibly error-prone, but still somewhat faster and more convenient than switching to the target branch and then merging from the branch I've just been at.

   What I'd like to see is when I right-click on another branch/changeset (that I'm not on) that I get the option "Merge to this branch/changeset...".

   This might seem like a small improvement, but given how often we do this, it'd definitely help. An option setting to also then switch to the target branch when doing this might be a plus (I noticed someone else asked for this before).

   Our usual workflow is to first merge from main to the current branch, sort out merge conflicts, check the build, etc., commit fixes and changes if needed, and then merge back to main.

   Currently, when I'm on a branch and I want to merge what I have to another branch (e.g. main) I have to right-click on my current branch/changeset, select "merge from this [] to..." and then pick the target from an endless list of all my braches.

   This is incredibly error-prone, but still somewhat faster and more convenient than switching to the target branch and then merging from the branch I've just been at.

   What I'd like to see is when I right-click on another branch/changeset (that I'm not on) that I get the option "Merge to this branch/changeset...".

   This might… more

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Option to revert pending changes when switching workspace

    When trying to switch the workspace to a different changeset/branch, the user is first asked if he's sure, but then gets an error if there are pending changes.

    It would be great if the question dialog would show how many pending changes there are (and maybe a tooltip with a list of all changed files?). Then, if the user decides to go through with it anyway, the pending changes should be reverted (maybe have a checkbox, so the user is really sure) and the switch should be performed.

    When there are no pending charges, the switch should just happen without asking.

    I often have loose files that got changes by the IDE or Unity that I can safely discard. Having to do this manually every time can be quite annoying when quickly zapping through different changesets.

    When trying to switch the workspace to a different changeset/branch, the user is first asked if he's sure, but then gets an error if there are pending changes.

    It would be great if the question dialog would show how many pending changes there are (and maybe a tooltip with a list of all changed files?). Then, if the user decides to go through with it anyway, the pending changes should be reverted (maybe have a checkbox, so the user is really sure) and the switch should be performed.

    When there are no pending charges, the switch should just happen without… more

    •  

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    5 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Support a 'Focus in Workspace Explorer' option in all context menus for a file

    Support the ability to jump to a file in the Workspace Explorer from any of the file dialogs. This includes: Pending Changes, Changeset Diff and others.

    Right now it is time consuming to see a file in pending changes and want to know more about the other folder contents where that file is located.

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Branch Explorer - Adjust text size of "branch bubble" in settings

    In branch explorer I zoomed a bit of, to have a greater overview. Unfortunately, the text bubbles above each branch getting smaller. So it's quite hard to read it then.

    Could it be possible to adjust the size in the side panel > Display options?

    •  

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Jira Next-Gen project integration

    Plastic integration with Jira Next-Gen projects is broken. There is no way to send data back to Jira projects from Plastic. There should be a Jira plug-in to make the set up for this not only possible but easy.

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Display status of remotely locked files in Plastic SCM Workspace Explorer (not just in Gluon)
    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. auto suggest releveant word (ie filenames / new files) in commit message

    many git and snv tools (gitextensions for example) do this and it makes writing useful commit messages much faster

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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 to limit some members of the team to certain submission folders.

    A whole lot of manual permissions work could be avoided by separating repository read / view permissions.

    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… more

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Ability to purge specific files

    I think we've all been in the situation where someone checks in multiple GB of images, and nobody notices just how much of a problem that is until later, when those files are properly reformatted and probably renamed.

    What happens after this point, currently, is that we wind up with an extra few GB of old data sitting around on the cloud server, costing money and making everything slower as well, but this is truly data we'd never need to see again.

    There are also cases where we try something out, then decide against that approach, but we want to delete specific files -- and truly purge them -- rather than having to delete entire changesets (which we can do, which is great).

    This sort of thing tends to be almost exclusively in the realm of textures and meshes, but there are a few other use cases depending on your project. Raw mocap data that is unexpectedly large, and then the nice optimized version that is cut down and has a lot fewer keyframes. Etc.

    For code and other text assets, it is clear we would generally never want to purge anything -- that's the entire point of scm. But for various forms of binary data, the ability to purge by-file would be a great way to allow for experimentation in the art, animation, and sound areas, while then getting rid of things that are not long-term needed.

    I think we've all been in the situation where someone checks in multiple GB of images, and nobody notices just how much of a problem that is until later, when those files are properly reformatted and probably renamed.

    What happens after this point, currently, is that we wind up with an extra few GB of old data sitting around on the cloud server, costing money and making everything slower as well, but this is truly data we'd never need to see again.

    There are also cases where we try something out, then decide against that approach, but we want to… more

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Preview (or show draft of) a merge

    I used to work with Azure Devops and what I miss the most is being able to preview a merge (or to create a draft of a merge).

    The idea behind this is that you see the actual changes when a branch would be merged. I have two reasons for this request:

    1. Currently with plastic you cant exactly see what the code will look like after a merge. When you currently do a code review, you don't know what the code will look after all conflicts are resolved.

    2. When a (feature) branch exists for a longer time, it's common to merge main into it occasionally. This avoids the branch from "getting old" and decreases the chance for conflicts in the future. But currently, when you want to review a branch, you don't know which changes are from the branch itself and which changes actually came from main. This makes a code review almost impossible when main has been merged into it a couple of times. I would really like to preview the merge, so I only have to look at the actual merge changes.

    I'm aware that you could merge a branch with main and look at the actual changes before clicking the Checkin button. But I can only do that after I resolved the conflicts. And the owner of the branch should take care of the conflicts, not the reviewer.

    I really really hope this feature will be a part of Plastic at some point :)

    I used to work with Azure Devops and what I miss the most is being able to preview a merge (or to create a draft of a merge).

    The idea behind this is that you see the actual changes when a branch would be merged. I have two reasons for this request:

    1. Currently with plastic you cant exactly see what the code will look like after a merge. When you currently do a code review, you don't know what the code will look after all conflicts are resolved.

    2. When a (feature) branch exists for a longer time, it's common to… more

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Add shortcut to Undo (Ctrl+Z) in the Pending Changes view

    It would be really helpful to have a shortcut bound to the Undo command, like Ctrl+Z for example, or a customizable one.

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. flatpak instead of distribution specific installers for linux

    It's 2022 and i still can not install Plastic on any Arch Linux based distribution. If you used Flatpak you would create a single package for literally every distribution with flatpak.

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close