526 results found

1. Support Multiple Search Terms in Workspace Explorer

   Searching in Visual Studio allows me to set multiple search terms separated by a space in order to better narrow my results. This is helpful if you aren't sure if the name of the file is "ProjectXMLData" or "ProjectDataXML", but you know for sure it has Project and XML in the name.

   Attached Images
   - VSSearch01 - Shows searching for all 'project'
   - VSSearch02 - Shows adding 'xml', but not as an exact match. The results are still displayed as expected
   - WSSearch01 - Shows searching for 'project' and results show as expected
   - WSSearch02 - Shows adding 'xml', but no results are returned

   Searching in Visual Studio allows me to set multiple search terms separated by a space in order to better narrow my results. This is helpful if you aren't sure if the name of the file is "ProjectXMLData" or "ProjectDataXML", but you know for sure it has Project and XML in the name.

   Attached Images
   - VSSearch01 - Shows searching for all 'project'
   - VSSearch02 - Shows adding 'xml', but not as an exact match. The results are still displayed as expected
   - WSSearch01 - Shows searching for 'project' and results show as expected
   -… more

   •  

   •  

   •  

   •  

   9 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

2. Better handling of dark theme in Linux

   Using a dark theme with the linux build ends up with some pretty glaring white backdrops to things and lots of unreadable text.

   It seems Plastic isn't using the supplied gtk theme colours, but instead has hardcoded colours for certain things.

   12 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

3. Maintain/Display the change comments for Rename function

   Hi,
   We've recently had to rename a bunch of our files, and we were applying comments at check-in (because it was required), but have noticed that after the Check-In, the History will show the Move action, but no longer display the comment attached.

   This would have been useful for us, as the comments kept track of some important information around why the renaming was happening, but this info is either lost/not displayed.

   Cheers.

   3 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  ·  Edit…  ·  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. 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

5. Improve merge changes context menu descriptions

   It would be nice if the context menu descriptions when resolving a merge conflict would be more informative.

   I'm referring to "Merge keeping source changes" and "Merge keeping workspace changes". The user has to know exactly which one is which, making this very error-prone.

   I suggest using "mine" and "theirs", as is common in other tools, or if possible, the name of the branch of each version.

   So "Merge keeping changes from 'main'" and "Merge keeping changes from 'main/fix-163'" would be much more informative.

   •  

   3 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  ·  Edit…  ·  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 an option to not merge formatting automatically

   I could not find an option to merge files manually when source has formatting and whitespace changes. These changes are lost after an auto-merge.

   3 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. "Add existing workspace" button

   On the workspaces tab, next to "Create new workspace..." a button "Add existing workspace" would be amazing.

   Use case: I recently received a new laptop and all of my working files were copied from my old laptop including a folder containing numerous workspaces that are >10gb each, I needed to work on some of these projects while out of the office but couldn't find an easy way to add them back in to Plastic and recreating/downloading them from scratch while remote wasn't an option.

   16 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

8. Implement cloud-based backups for Plastic Cloud

   I propose that Plastic Cloud offers an incremental backup method. It should export backup data to customer-provided cloud storage (AWS S3 / Google Cloud Storage / Azure Storage), perform backups with high frequency (possibly with a combination of full / incremental backups), and only leave the responsibility of validating these backups with the customer.

   Our use case:

   We use Plastic Cloud instead of Plastic Server, because it reduces our operational overhead. Plastic Cloud is great in many ways, but using it means that we also entrust the responsibility of availability, security, as well as backups/disaster recovery with Codice Software.

   As our organization grows larger and older, we need to have shared responsibility for backups/disaster recovery. If we ask ourselves, "do we have backups?" then we must be able to answer "yes, and we have verified that they are not corrupt", not "yes, we trust that another organization does it for us".

   It is possible to handle backups today: run a local Plastic Server, scan the Plastic Cloud organization, replicate what's in there to local repositories, then archive the local repositories. However, that requires a fair bit of operational work.

   I would like to see that Plastic Cloud offered an 'automated backups' feature: I provide details on a customer-controlled cloud storage bucket in a cloud provider like AWS/GCE/Azure, and credentials that allow Plastic Cloud write-only rights to the bucket (without the rights to modify what's already in the bucket). Plastic Cloud would then regularly export changes to the bucket. For example, a full export once per month + an incremental export once per day. I would like notifications to be sent to me (for example via emails) whenever there is a problem with export process, as well as summaries of this somewhere (for example within the weekly digest emails that are sent out).

   I would like validation to be left with the customer (although someone will probably ask for some degree of automation here as well). As such, I expect that I can restore a backup - or perhaps part of a backup, like, only a single repo - into a local Plastic Server and then be able to access the contents directly.

   The automated "export to cloud storage bucket" process will allow us to easily implement any process we would like for further backups (for example, manually copy backups from cloud bucket to offline storage).

   It would be helpful to be able to be able to get some idea of the contents of a backup without needing to perform a full restore. (Example: which repos are inside the backup? what is the range of changesets contained within the backup?) This could either be a tool that inspects the backup files itself, or additional text file(s) that are written at the time when the backups are created.

   One nice side effect of a backup mechanism like this is that it provides us with the ability to recover from some of our mistakes, that would otherwise require contacting Codice support.

   The feature requires additional backend-side processing and network transfer. We are happy to pay extra for this.

   (Slightly related, there is a cloud-to-cloud backup service for GitHub: https://backhub.co/ - this has a much broader featureset than suggested above, but it demonstrates the core need.)

   I propose that Plastic Cloud offers an incremental backup method. It should export backup data to customer-provided cloud storage (AWS S3 / Google Cloud Storage / Azure Storage), perform backups with high frequency (possibly with a combination of full / incremental backups), and only leave the responsibility of validating these backups with the customer.

   Our use case:

   We use Plastic Cloud instead of Plastic Server, because it reduces our operational overhead. Plastic Cloud is great in many ways, but using it means that we also entrust the responsibility of availability, security, as well as backups/disaster recovery with Codice Software.

   As… more

   13 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

9. Default ignore settings for Unity projects

   When starting a new project, allow the user to indicate that it is a Unity project, and enact default ignore file settings based on best practices. Allow the user to see which files will be ignored, and override them.

   3 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

10. Open file in file system

    When I view file changes in the Compare Revisions window, I often want to know the current state of the file or change it. Add an option to locate the file in local workspace if it exists locally. It's not the same as current option to open that revision in a temp. directory.

    3 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

11. Revert a changeset option in context menu

    In Git UI I used to be able to do a simple task of reverting a selected commit locally. I saw an option to delete a changeset in Plastic, but sometimes you don't have a permission but you need to revert all the changes without opening any Diff windows and selecting any individual files.

    3 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

12. 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

13. Allow for display of branch attributes in the branch explorer window

    In the branch explorer view you have essentially two sections. The graphical chart on the left and the properties panels on the right.

    Assigning attributes to branches is very handy for keeping track of things like status and work type, but currently you can't see those attributes "in a big picture" as you have to click on the branch and then look at its attributes in the right hand panel.

    What about allowing us a Display Option to draw the attribute name and value in the main chart right underneath the branch? This would allow for seeing the information on multiple branches at a glance and help with the big picture.

    In the branch explorer view you have essentially two sections. The graphical chart on the left and the properties panels on the right.

    Assigning attributes to branches is very handy for keeping track of things like status and work type, but currently you can't see those attributes "in a big picture" as you have to click on the branch and then look at its attributes in the right hand panel.

    What about allowing us a Display Option to draw the attribute name and value in the main chart right underneath the branch? This would allow for seeing the information on… more

    4 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

14. Pending changes checkboxes need to be half filled if you haven't selected every child item

    •  

    3 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

15. Autofill & Disable "Server" field when "Use relative server" is checked in XLink dialogue

    When I am in a workspace that is linked to SomeRepo@SomeCompany@cloud, and I create a new XLink, the XLink dialogue by default has Target Server set to local, and Use Relative Server set to true. These are incompatible! Either relative shouldn't be checked by default, or the server default should match the workspace's server. I think the latter option is more convenient for most use cases.

    1 vote

    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

16. [gmaster] Support for git-worktree

    Would be great if Gmaster would support git-worktree
    It could be solved in similar way as in PlasticSCM - creation of different workspaces for same repository

    3 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  ·  Edit…  ·  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. experimental checkin feature for gluon

    I hear from my designer-y people that they'd like to be able to experiment with features before checking them in to the cloud. Naturally this can be done with branches with the regular plastic, but I'd like for them to keep utilizing the simplicity of gluon.

    I don't have a solid suggestion as to how to implement this, but as an alternative to checkin you could provide a "experimental checkin" action. Gluon still behaves as normal, but these checkins are only present for the user. When the user is done experimenting, they can checkin their experimental changesets to the cloud or abandon them alltogether.

    Like I said I don't know if this is feasible, but it would be a handy tool for the linear workflow gluon provides!

    I hear from my designer-y people that they'd like to be able to experiment with features before checking them in to the cloud. Naturally this can be done with branches with the regular plastic, but I'd like for them to keep utilizing the simplicity of gluon.

    I don't have a solid suggestion as to how to implement this, but as an alternative to checkin you could provide a "experimental checkin" action. Gluon still behaves as normal, but these checkins are only present for the user. When the user is done experimenting, they can checkin their experimental changesets to the cloud… more

    1 vote

    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

18. Provide changeset-id's in update triggers

    Now, the update triggers only provide a path to the workspace being updated.
    Having access to the old and new changeset-id's opens up quite a lot new possibilities.

    For example, in UE4, when working with plugins in a code project, they are compiled automatically at first. When making code changes to the plugins, they are often not automatically detected which causes the engine to crash at startup.
    Deleting two specific folders makes the engine recompile those binaries automatically and thus fixes this inconvenience. Unfortunately, this process takes about 5 minutes on average so doing it after every update is not feasible.
    By providing a specific string/tag in the comment of checkins that require a compile, we are able to only recompile when necessary.

    In order to make this work, we have to write out the current changeset-id to a file in the before-update trigger. Then in the after update trigger, we get the current one. Finally we would use the find command to get all changesets in between those two and check if any of their comments contain the tag.

    We are already able to access the current changeset-id with
    cm status --nochanges
    and some parsing. (Although this could be made easier.)
    Thus, only exposing the future changeset-id in before-update and the previous changeset-id in after-update would suffice.

    Thanks in advance

    Now, the update triggers only provide a path to the workspace being updated.
    Having access to the old and new changeset-id's opens up quite a lot new possibilities.

    For example, in UE4, when working with plugins in a code project, they are compiled automatically at first. When making code changes to the plugins, they are often not automatically detected which causes the engine to crash at startup.
    Deleting two specific folders makes the engine recompile those binaries automatically and thus fixes this inconvenience. Unfortunately, this process takes about 5 minutes on average so doing it after every update is not… more

    15 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

19. Marked branch always visible

    "Marked" branches should always be visible, even when they don't have any new changesets in the last couple of days/weeks so that I don't have to scroll back for a merge.

    This could be achieved by sticking the last changeset of a "marked" branch to the left edge of the branch explorer

    4 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

20. Support clearing the update report output (Gluon)

    Add an option to clear the report window output display in the context window for the update report pane

    1 vote

    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