531 results found

1. Please support cloud trigger for MS Teams

   Hi, our company switched from Slack to MS Teams, but unfortunately, the plastic cloud trigger function does not seem to be properly supported at MS Teams.

   MS Teams is also a program with as many users as Slack. We hope that MS Teams will be supported through MS Teams's 'Incoming Webhook' connector, just as you have supported Slack and Discord.

   We think it will be easy for you. However, I think the benefits will be great for companies using MS Teams. I hope you will consider this positively.

   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

2. add report bug and suggest feature menu item on the left

   it would be nice to be able to click one of these menu item icons to open up a window to enter this info in. I think this will help iterate on user feedback.

   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…)
   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. Add standard "File", "View" etc. menu bar

   All Windows and Mac applications have a standard "File", "View", "Help" etc. menu. The current left-hand menu is fine, but "Preferences" and "About" should be removed and moved to a new standard menu.

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

4. Sync with server

   Quite simple, sync with server button which completely wipes out any local changes and restores a workspace to whatever changeset that you are on.

   We have to implement batch files to clean up things on the client side which get generated when we switch around from branch to branch, and it would be nice to have a button in the GUI alongside update workspace, that says sync to the server.

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

5. Bring back workspace ListView option
   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…)
   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

6. Branch explorer: Keep text readable when zooming out

   Hello.

   Currently if I want to zoom out to see more than a day or 2 of changes in the branch explorer, the text becomes so small it's completely unreadable.

   I propose that the text for branch name / description, and date headers at the top, should remain the same size (or at least get capped at a minimum size) when zooming out, so that it is still readable.

   There is plenty of space to fit the full sized text.

   •  

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

7. Filtering by branch name doesn't work anymore in version 4

   Main or head branches used to end with a # symbol in version 3.0. You could use this in the filter to to only see things related to that branch. In version 4.0 they no longer end with that symbol, so you cant filter out sub branches since they all start with the main branch's name.

   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…)
   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. Merge as an atomic operation

   There might be some use-cases out there for not wanting to do this, When I merge one branch into another branch, if I make a change in between finishing the merging and checking in my changes, that change becomes very difficult to trace as to when it happened. If that change breaks something it becomes nasty to track it down and then revert it.

   There are probably use-cases where people wouldn't want that behavior but I'd like to be prompted to go to pending changes and check-in my merge once it's finished.

   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  ·  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. export item revision

   When browsing a branch or changeset for items it sometimes would be nice to save a file/folder to some place on the disk.

   Some files belong together and if I want to view or even execute these files I need all of them with correct filenames in the same place.

   Clicking on a item in plastic opens this file with the system standard viewer in a temporary directory. Depending on the file this may not be a good idea! Therefore I need a way to select some items (files/folders) and export 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…)
   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

10. filter CS by label

    filter CS by label will enable to connect Xlink much easier

    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

11. Add branch support to explorer plug-in

    The explorer plug-in works very well for managing a workspace, however, there is no branch support.

    1) No way to tell what branch the workspace currently has
    2) No way to switch the workspace to a particular branch
    3) No way to merge the current branch into another
    4) No way to merge another branch into the current one
    --there are other branch features available, but these are the ones my team uses the most.

    All of these thing currently require the GUI to perform, but could be done using the Explorer plug-in

    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

12. don't select items when searching in branch explorer

    "Show selected branches in a new diagram" is a useful way of making sense of a large and complex history but first you have to find the branches to select.

    The obvious way is to use the search field, but this changes the current selection to what if finds, losing you previous ones. It would be better if it just centred and highlighted the item without selecting it.

    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

13. Add three enhancements to the pending changes view when merging...

    1. If a pending merge results in no actual file changes, it doesn't seem possible to back out of the merge if it's not the desired result: the merge link can't be undone without at least one change to a file in the pending merge.

    I got into this situation doing a sophisticated merge; a directory in the source branch had been deleted, but a new file has been added on the source branch in that directory that I wanted to merge over into a different location on the target branch.

    I chose the merge conflict resolution of preserving the delete for the directory (I had forgotten about the new file) - once I realized my mistake, I couldn't back out of the pending merge.

    I tried forcing an undo by shelving and undoing via the shelve - this led to an internal of-by-one indexing error in Plastic.
    I also tried switching my workspace to another changeset, hoping that might break the merge link - but Plastic moves the merge link to the new changeset (which is actually the right thing to do).
    I also tried committing the pending merge to a new branch with the intention of deleting the branch and thus losing the merge changeset - but this was blocked by Plastic.

    In the end I had to destroy the workspace and start a new one - this wasn't that big a problem, as I had no changed files, but is inconvenient.

    So it would be good to extend the undo functionality to remove a pending merge link in the absence of file or directory changes.

    1. I managed to make a poor commit when I made another merge, which went ahead automatically, but had to do some manual edits in the changeset to get my project to build properly - this was not the fault of the merge, simply a case of extra steps being necessary to get a correctly working result. Plastic doesn't monitor externally-made changes in the workspace when one works in the Plastic GUI, so I didn't see some files that had changed due to reconfiguring the NuGet dependencies in my Visual Studio solution. As a result I committed, it which point the GUI updated and showed me the additional changed files that should have been in the commit in the first place. The end result was a broken commit followed by a 'patch-up' commit. Not the end of the world, but messy.

    Add an internal pre-commit check in Plastic that re-scans the workspace, popping-up a warning if new pending changes are detected that are not in the commit (or even if the files in the commit have changed from the deltas that Plastic thinks it had at the start of the commit). The workspace view would update before the pop-up, rather than wait until after the commit.

    I know that continuous pro-active scanning of the workspace is not something you guys wish to consider, and that makes sense to me - this is just a one-off done as a built-in pre-commit hook.

    1. Sometimes it's handy to reject changed files individually when doing a merge that has proceeded automatically without conflicts. At the moment I can't do this, because attempting to undo the changes on a single file makes Plastic want to delete the merge link. This makes sense 98% of the time, but would it be possible to tell Plastic when it has successfully merged but has not yet committed to simply through away the changes on a merged file while still keeping the merge link? This is an extreme edge case of when one performs a merge, but needs to 'massage' the resulting files in the pending merge state prior to committing.

    Add a retrospective 'choose source or destination' option in the pending changes view when it is showing a pending merge.

    1. If a pending merge results in no actual file changes, it doesn't seem possible to back out of the merge if it's not the desired result: the merge link can't be undone without at least one change to a file in the pending merge.

    I got into this situation doing a sophisticated merge; a directory in the source branch had been deleted, but a new file has been added on the source branch in that directory that I wanted to merge over into a different location on the target branch.

    I chose the merge conflict resolution of preserving the delete… more

    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

14. Additional Pending Changes Functionality

    I would like to have the ability to compare the current workspace, including pending changes, against a custom checkin. This is useful if I need to revert specific changes made in a branch back to mainline, and I want to see if the reversions I've made have been effective before checking in the code.

    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

15. flag changesets that won't be merged

    It would be useful to be able to set a flag on a changset such that it won't be merged from the branch it exists on (by merging from a subsequent changeset, although cherry picking it could possibly be an exception).

    I sometimes need to make temporary changes on a branch (eg. for testing), but don't want to risk these getting merged upstream.

    Normally I do periodic checkins of all changed files, so need to be careful to exclude these. It would be nice for the temporary changes to be managed by the SCM in a safe way.

    I don't know if something similar could be achieved via custom change lists, but for some reason the 'Move to changelist' option is greyed out.

    It would be useful to be able to set a flag on a changset such that it won't be merged from the branch it exists on (by merging from a subsequent changeset, although cherry picking it could possibly be an exception).

    I sometimes need to make temporary changes on a branch (eg. for testing), but don't want to risk these getting merged upstream.

    Normally I do periodic checkins of all changed files, so need to be careful to exclude these. It would be nice for the temporary changes to be managed by the SCM in a safe way.

    I don't… more

    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

16. Repository branch templates

    There are many branching scenarios that people use. But it would be nice to have a default template. And template libraries.

    Example when I create a repo I also rename main to Production and create Test and Development branches.

    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

17. Icon for files added to source control but not checked in

    Icons in Windows Explorer for files that are currently added to source control but haven't yet been checked in.

    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

18. Plugin for SQL Server Management Studio (SSMS)

    A plugin to allow integration of the following features in SSMS:
    -change commits
    -annotated files
    -revision history on a file
    -workspace explorer
    -branch explorer

    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

19. Different display settings for 2 workspaces that refer to the same repository

    I have 2 workspaces that refer to the same repository. To get an easier view of the diagram, I tried to set the display options differently to show particular branches for each workspace. It seems imposible to have different display settings

    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

20. Horizontal comparison panes in diff viewer

    Would you consider adding optional horizontal comparison panes to the diff viewer, displayed or hidden with a button or a key combination?

    It becomes useful when there are changes in long lines. Thanks to them you don't usually have to scroll the window in order to see all changed areas. This idea comes from WinMerge, which has both vertical and horizontal comparison panes.

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