Settings and activity

  1. 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Rando Wiltschek commented  · 

    Yeah, I suppose so. A quick way to sort small changesets into the correct branches.

    In plastic I can't easily switch to the right branch, commit my fix and move back, since I have to undo all my changes in order to switch.

    Without that limitation (it never was an issue for me with mercurial and SourceTree), it wouldn't be necessary, I suppose.

    Rando Wiltschek shared this idea  · 
  2. 34 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Rando Wiltschek commented  · 

    I thought so, but I couldn't find the suggestion.

    Rando Wiltschek shared this idea  · 
  3. 36 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Rando Wiltschek supported this idea  · 
  4. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Rando Wiltschek commented  · 

    Ah, I get you. Although given the overloaded context menu that we currently have, I don't think another option will be faster than double clicking a changeset and clicking "I'm sure".
    But maybe holding shift like with the windows delete function might be a good compromise for experienced developers who need this often.

    An error occurred while saving the comment
    Rando Wiltschek commented  · 

    I don't quite understand how your suggestion is different. Can you elaborate?

    Rando Wiltschek shared this idea  · 
  5. 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Rando Wiltschek shared this idea  · 
  6. 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Rando Wiltschek commented  · 

    Great, thanks!

    Rando Wiltschek shared this idea  · 
  7. 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Rando Wiltschek commented  · 

    I second this. Maybe optionally (per attribute) without the attribute name. For example, I'd like to see the "status" attribute as soon as it has any value: E.g. just "Done" or "Rejected".

    In the plastic guide book the attributes are actually shown in the generalized examples. That's more or less exactly what I'd want.

    Also having a color per attribute type (or even value?) would be useful too. So we can have "status = done" in green or "status = rejected" in red, and so on.

    Rando Wiltschek supported this idea  ·