General

General

Categories

JUMP TO ANOTHER FORUM

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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…

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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…

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. "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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add an option to clear the report window output display in the context window for the update report pane

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Currently the Gluon Update Report pane displays the timestamp at the beginning of the report. This means that to find out the last time you synced you have to scroll up through a variable, and sometimes large, list of entries to find the timestamp while making sure that you don't overshoot it and end up in the previous update report.

    I suggest moving it to the end of the report where the most recent sync time can always be easily found and quickly accessible.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. If you have a file in your Checkin changes tab that is Changed but not checked out, you currently have to switch to the Explore workspace tab and navigate to the file, then check it out.

    I would like to be able to bring up the context menu for the file under the Checkin changes tab and choose Check out.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Since using branches for tasks is the preferred workflow I think it'd be useful to be able to copy the branch name from the changeset ui so we can easily goto our project management software.

    or at the very least a way to go directly to that branch from the changeset view instead of having to look for it.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. When I use a local repo, i should to download all branch-related data locally. Then i don't need it anymore (for example, it is rejected branch or we totally switch to the new parallel branch, or something else). But I have no ability to locally remove them. I fully understand that deleting branches from repo could cause troubles for whole tree, but what if i remove only local copy of that changesets/branches?

    Of course I can locally remove all changesets and then whole branch, but it is such uncomfortable and if later i will want to switch back - it…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?