526 results found

1. show branch name in workspace tab tool-tips

   Currently the tool-tip shows the workspace path. All my workspaces are in a common directory so this isn't very useful to me. Knowing what branch it selects before switching to it would be.

   5 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

2. Tabs groups / Project managment

   It would be really handy to be abble to manage groups of tabs like in some "projects groups".
   It would allow on left navigation panel to create/select "groups" and it would display a set of tabs (like last openned in this group).

   We are managing tens of projects and have often several repo for each. At this time we're only abble to see first character of each tab name and have to scroll most of the time.

   At least several rows of tabs would be a first step of improvement :)

   Jean-Luc REY

   7 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

3. Amend commits

   As git user, more than once i find the need to fix something added to a comit, using the --amend parameter. It would be great to have this feature on plasticscm, because otherwise i end with

   D - E - F
   \
   A - B - C - Fixes C

   102 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…)
   11 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. 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

5. Show full history of an item in History view (and History as 2D tree)

   The History view and History as 2D tree view do not contain merges affecting the item and do not show any reverts. Therefore those views are not really a history, but only a list of different variants of the item existing in the history.
   See comments for a deeper explanation.

   46 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

6. Too general confirmation message when deleting an object

   Whenever you try to delete a repository, workspace, an attribute etc., you have to confirm that operation. But the confimation message box does not tell you what you are actually deleting. At that point I always click "No" to abort the operation, make sure I really selected an appropriate item and then attempt deletion once again.

   It would be better if that kind of messages named the object being deleted. The infomation like "Deleting 1 object(s)" causes a risk of deleting something else than the user really expects.

   8 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. Branch Explorer: option to display branch owner

   What do you think about adding an option to display branch owner next to each branch*? It would give us an overwiew of which people are working on a given project at a given moment. In our company the branch owner is almost in all cases the person that performs the task associated with the branch.

   • I know the information is available in branch properties, but the thing is that we need a more general view without having to select branch to see its owner.
   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

8. add branch explorer menu to 'Branches' tab

   It would be useful to add the various 'Show selected branches ... in diagram' from the 'Branch Explorer' tab as a context menu to the table of branches on the 'Branches' tab.

   It can be hard to find the branches of interest in the explorer, but the filter for the table view makes this much easier. The table already helpfully maintains your current selections when you change its filter, so it is easy to build up the group you want.

   24 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

9. collapse all in branch diff

   I just checked out the latest feature: showing merge information in branch diff. Very nice ;)
   One little improvement would be a “collapse all” button, as my branch is kind of old and shows a lot of merges.

   5 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. Add Image List to the workspace tab control

    Add Image List to the workspace tab control using the images from the actions to indicate the function.

    On Branch Explorer tabs then show just the repo information text vs "Branch Explorer for repository..."

    Given Xlinks in a project I may have 3 or 4 Branch Explorers open at a time and the tabs all say "Branch Exporer f..."

    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

11. compare contents as well as timestamps for changed status

    Currently the option is instead of timestamps. It would be faster just to check the contents if the timestamps don't match (unless it already does and this is just a labelling issue).

    10 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…)
    planned  ·  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. Show at least one changeset in queries

    With some (external) repositories last changes are sometimes so long ago that nothing shows up in for example the xlink changeset selector.

    So please show at least the last release if the query does not return results. This behavior should also be implemented for other query based views. Maybe with a switch in the preference to turn it on/off.

    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

13. Checkin comment and Code review text boxes (scrollbars, Ctrl+A)

    A commit message text box and a code review text box does not have any scroll bar, does not allow scrolling with a mouse and does not allow Ctrl+A (select all text). All these things would be useful.

    This suggestion has been added here already (https://plasticscm.uservoice.com/forums/15467-general/suggestions/4341465-checkin-comment-and-code-review-text-boxes) but it was marked as completed even though it is still not working.

    See also the original post here: http://www.plasticscm.net/index.php?/topic/1291-some-ux-issues/#entry10137
    There is also another suggestion close to this explained by a picture (partially displayed lines).

    28 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

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

15. Show labels in changesets view; or show changesets in labels view

    In "Changesets" tab it is possible to right click on a changeset and select "Label this changeset"
    However nowhere in this view can I see if there is a label against a changeset- there are columns for Changeset's Name, Comment, Date , branch et al but not even the "Show Extended Information" shows anything about labels.

    Why this would be useful:
    In my typical workflow I make changes as development proceeds with comments stating what & why things have been done; often with references to issue#s . For example "Fix issue#5341 the conblogminator was crashing with error E54 when the user metaed the cokebottle" or "Merge SQL refactoring from test branch" or whatever.

    When a release is made, then I label the last changeset with a name such as "Release 0.9.7" and a comment might be "installed in production on 16/9/2013"

    Now I want to send a message to my client saying what just changed. Ie I would like to see all the changeset comments between the previous label (0.9.6) and the new one (0.9.7)

    To do this I have to go to "Other Actions -> Labels" , look at the change set numbers involved, then go back to the change set view and read the comments.
    This is even messier if there are multiple branches involved.

    This process would be greatly simplified if the label name (and ideally comment) were accessable from the changeset view OR if there was a way to view the changeset history from the labels tab.
    You can Diff between two labels but this only shows the detail of the file changes, not the changeset information.

    (Note the UI for diffing between two labels isn't perfect, it seems intuitive to me to select the two labels, with Ctrl-Click perhaps - this is possible now - and then press Ctrl-D to view diff, but doing that, the right-click menu is entirely disabled (and no Ctrl-D shortcut anyway). YOu have to select one label, right click and choose "Diff with other label" and then select the label from a list, which is relatively clumsy
    This belongs as a separate suggestion of course)

    In "Changesets" tab it is possible to right click on a changeset and select "Label this changeset"
    However nowhere in this view can I see if there is a label against a changeset- there are columns for Changeset's Name, Comment, Date , branch et al but not even the "Show Extended Information" shows anything about labels.

    Why this would be useful:
    In my typical workflow I make changes as development proceeds with comments stating what & why things have been done; often with references to issue#s . For example "Fix issue#5341 the conblogminator was crashing with error E54 when the… more

    41 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

16. Plugin for Webstorm IDE

    Support for VCS PlasticSCM under vcs roots and possibly Webstorms internal changelist, auto checkin and checkout support for editing files. Could be adapted easily from existing IntelliJ plugin to support Webstorm and PHPStorm?

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

18. Add a context menu to the 'Checking pending changes' window

    There is no context menu available for changed files in the 'Checking pending changes' window. However, there is a similar view in the 'Pending changes' tab of PlasticSCM's main window and a context menu is available there.

    The thing is that the context menu enables you to view changes using a diff tool you prefer (the one set in application preferences). In the window mentioned in the topic there is no such menu at all and you can view changes only using the diff tool embedded inside that window.

    Most of us in our company are used to WinMerge and we would like to continue using it with PlasticSCM. The 'Pending changes' view enables you to do that, but I think you rarely use it when managing source code changes directly from Visual Studio (which displays the discussed window).

    There is no context menu available for changed files in the 'Checking pending changes' window. However, there is a similar view in the 'Pending changes' tab of PlasticSCM's main window and a context menu is available there.

    The thing is that the context menu enables you to view changes using a diff tool you prefer (the one set in application preferences). In the window mentioned in the topic there is no such menu at all and you can view changes only using the diff tool embedded inside that window.

    Most of us in our company are used to WinMerge and… more

    14 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. goto child changeset

    In branch explorer there is a 'goto parent changeset' context menu. A similar one for children, possibly listing multiple branches, would be useful. Navigation is quite difficult in this direction.

    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…)
    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. Sync, Repos and Workspaces on their own tab

    Hi,

    Since the latest release it's possible to close the tabs in the caption area.

    Great feature but I would like one more enhancement, a non closeable tab (preferably the first tab on the right) that contains non workspace related subtabs like Your Workspaces, Your Repositories Rss Notification and Sync replication (not sure about Shelves).

    This way the workspace related tabs stay cleaner (and smaller).

    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…)
    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
    started  ·  AdminCodice Software (CEO / Founder, plasticscm) responded

    Actually we started doing this on the new Mac and Linux GUIs :-) The new GameUI also supports this mechanism. Soon we’ll have it on the regular Windows GUI.