Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

531 results found

  1. It would be nice to be able to search database files for their contents, and accross history.

    I am picturing a use case where a user would like to download the last changeset before a particular piece of source code was deleted, for instance. The user could search the repository for files containing that particular text, and the server would return the file names, and perhaps the first and last changesets where the text still appeared in the file.

    6 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. It would be great to see all attributes set on a branch somewhere else then the 'attributes' panel. Not I have to change the side panel from 'Properties' to 'Attributes' to see which attributes are set on a given branch.
    To speed this up, it sure is nice to see attributes in the branch tooltip.
    What you'd say about that?

    23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. After performing a merge it would be useful if the pending changes had some merge specific content:

    1) show which files were merged entirely automatically and which required manual intervention. Currently the 'Status' column shows "Replaced / Merge from ..." or "Checked-out / Merge from ...". I'm guessing the replaced corresponds to files that only changed on the source and checked out is for both manual and automatic merges?

    2) Provide menu items for comparing the merged file (workspace revision) to one of: base, source, destination. Currently "Diff revisions..." defaults to the last but does not make it easy to…

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. I'd like to be able to split existing changesets, similar to what is possible with 'git rebase'.
    Mostly this is useful for preparation for cherry-picking some functionality that is needed on more than one branch.
    I'm not suggesting that you necessarily inflict something as complexed as 'git rebase' in plastic.

    Instead it might take the form of:

    A. Do a subtractive merge of the commit I want to split. Allow me to then re-merge the subtractively merged commit, without generating any merge links, over the current changeset (or maybe invent some kind of new merge link that visually indicates this…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Currently, the listlocks command doesn't use what's configured in the lock.conf, making it confusing when using an external lock server. See this thread for more info : http://www.plasticscm.net/index.php?/topic/2064-exclusive-checkout-in-dvcs-configuration/#entry13367.

    6 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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…

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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…

    41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?