535 results found

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

   Submit Rating

2. 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 0 votes 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

   Submit Rating

3. 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 0 votes 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

   Submit Rating

4. 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 0 votes 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

   Submit Rating

5. 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 0 votes 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

   Submit Rating

6. 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 0 votes 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

   Submit Rating

7. 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 0 votes 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

   Submit Rating

8. 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 0 votes 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

   Submit Rating

9. 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 0 votes 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

   Submit Rating
   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.

10. option to cancel workspace update

    A workspace update can be quite slow, particularly if you made a mistake in cloaked.conf. Rather than killing the process, it would be nice to be able to cancel the update.

    22 votes

    Vote 0 votes 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

    Submit Rating

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 0 votes 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

    Submit Rating

12. Keep typed comment when closing checkin dialog without commit.

    Sometimes i type comment for a checkin but then discover some issues in the list of files that force me to close the dialog (loosing the already typed comments).

    The current woraround is to open notepad and copy the comment into it for later use. But that is rather clumsy.

    So request is that when you close the commit dialog without commit the typed comment is added to the dropdown list of previous comments (or is just restored when the dialog is re-opened for the same workspace).

    10 votes

    Vote 0 votes 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

    Submit Rating

13. option to select diff tool on the command line

    If you use a console based diff tool such as vimdiff it can cause the GUI problems. It would be nice to be able to set different difftool preferences for the GUI and 'cm diff', possibly with a command line option:

    cm diff --tool=vimdiff

    It might be necessary to give tools names or id's in the GUI preferences to reference from the command line so you can easily configure the arguments.

    9 votes

    Vote 0 votes 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

    Submit Rating

14. filter CS by label

    filter CS by label will enable to connect Xlink much easier

    3 votes

    Vote 0 votes 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

    Submit Rating

15. When entering visibility mode, it would be useful to keep conditional format colors rather than moving them to the navigator.
    12 votes

    Vote 0 votes 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

    Submit Rating

16. Improve integration with JIRA

    Develop a JIRA plugin for Jira, to improve visibility.
    Add options to create branches from JIRA and issues from PlasticSCM.
    Embed links to open each other Web Portal.

    In general, a text box in the Jira issue is not enough. The interaction should be smooth.

    69 votes

    Vote 0 votes 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

    Submit Rating

17. Client Silent Install in Active Directory

    Need a client silent Install with chosen components in active directory

    24 votes

    Vote 0 votes 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

    Submit Rating

18. Pull Requests

    Provide a mechanism to approve merges into specific branches.
    One option is to use pull requests with an approval mechanism (of one or more required approvals).

    This will allow trace-ability and enforcement of organization rules.
    Linking it to code review will make it even greater.

    (Check out Stash for examples)

    18 votes

    Vote 0 votes 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

    Submit Rating

19. Integrate the Repository configuration (plastic configuration wizard) with the Plastic UI.

    Currently, to use a different repository server, you have to run the configuration wizard multiple times.

    It would be much more convenient to be able to open the Plastic SCM tool and click "add new server..." or "select repositories from server..." so that the user can choose where to get a list of repositories (projects) to work with - and start creating workspaces to pull the project down to.

    The following is a scenario I ran into:
    1) I created a local plastic server to replace my personal CVS server for projects that I work on at home. Using the configuration wizard works fine for that - assuming I will only have a SINGLE plastic server.
    2) I decided that I wanted to ditch CVS/TFS at work and replace it with plastic - however, I also often work from home - now I have to configure my WORK server through the plastic configuration wizard. Which DROPS my original configuration. I can create workspaces from the NEW server, but have no ability to create workspaces on the "old" (meaning, personal/home) one until I switch the active server - by re-configuring it through the configuration wizard - thus dropping my Work server configuration.

    Currently, to use a different repository server, you have to run the configuration wizard multiple times.

    It would be much more convenient to be able to open the Plastic SCM tool and click "add new server..." or "select repositories from server..." so that the user can choose where to get a list of repositories (projects) to work with - and start creating workspaces to pull the project down to.

    The following is a scenario I ran into:
    1) I created a local plastic server to replace my personal CVS server for projects that I work on at home. Using the… more

    10 votes

    Vote 0 votes 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

    Submit Rating

20. Ability to copy new and changed files from a Diff... comparison

    When running a Diff... between changesets using Plastic GUI (say, when comparing the most recent changeset to the last published build), it would be very useful to be able to copy all new and changed files from the workspace to a specified target directory.

    4 votes

    Vote 0 votes 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

    Submit Rating