Skip to content

Chris

My feedback

5 results found

  1. 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)
    An error occurred while saving the comment
    Chris commented  · 

    Igor,

    Thank you for your consideration and feedback.

    I understand your concern about changing the fundamental behavior of the 'checkboxes'. However, I do not believe additional visual indicators would be the answer. As you pointed out, there's already an indicator and, at least in my case, it doesn't solve the problem. The rule problem is that there's a lot of precedence already in Windows (as well as Macs) for multi-selection (i.e. Shift-Click and Ctrl-Click). If your product could leverage that already built-in muscle memory, it would be more intuitive and easier for casual users to pick up.

    Rather than change the behavior of the checkboxes, maybe you could just enable an additional multi-select mode? For example, now, when I click on a row, the current row is highlighted in blue. Maybe I can use Windows multi-select semantics to keep highlighting additional rows in blue? Then, I won't be using the persistent checkboxes at all.

    An error occurred while saving the comment
    Chris commented  · 

    In thinking about this more, it would be nice if multi-select worked more like it does in windows. If I click on an the multi-select button on an issue without holding down the control or shift key, it resets any previous selection and starts a new one. Then, I can extend the selection by clicking on other multi-select button with the Shift Key or Control Key pressed.

    FWIW, the non-intuitive operation of the multi-select really makes Structure confusing for casual users. Even for power users like myself, I'm constantly getting bitten by this behavior.

    Chris shared this idea  · 
  2. 2 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)
    An error occurred while saving the comment
    Chris commented  · 

    Igor,

    Thank you for your input. I would argue that in both cases, i.e. weighted values are used or zero values are used, the Progress roll-up is suspect. Therefore, both cases should have a visual indicator. I think the same indicator would suffice. Thus, we could have a visual 'asterisk' if the Progress is 'incomplete' due to sub-issues not having estimates. If all of the sub-issues have estimates and the Progress is based on complete information, only then would the 'asterisk' be removed.

    For the 'asterisk' I would recommend something like the indicator that Excel uses whenever there's a comment on a cell. It's a tiny, red triangle in the upper left corner of the cell.

    Chris shared this idea  · 
  3. 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)
    Chris supported this idea  · 
    An error occurred while saving the comment
    Chris commented  · 

    I too would like this feature. Often, my users want to sort the issues visible in the structure according to assignee, priority, etc. They don't understand that ordering is significant in the structure view.

    It would be very nice if there were some way to open a particular set of issues visible in the structure view within the issue navigator. Then, users could sort to their heart's content.

    In particular, it would be nice if one could click on a particular issue in the structure and execute the following query in the issue navigator: issuekey in structure("Blah", "ancestor in [issuekey = ###]").

    "###" could be one or more issue IDs which were selected in the structure view.

  4. 2 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)
    An error occurred while saving the comment
    Chris commented  · 

    Igor, thank you for the consideration and exchange of idea.

    I completely understand your concerns about discontinuities in the displayed information when jumping from one context to another. Isn't that already the case, however? I'm not a structure expert, but I thought items in the structure would be filtered depending on the context. So, if I view the structure from the Version tab and, then, jump to a particular issue, I might suddenly see a lot more issues in the structure as the filtered context is lost.

    To my way of thinking, it would make perfect sense for the progress to be consistent with the issues that are visible in that context.

    Perhaps you could provide a button to switch between context-aware and context-free progress when viewing the structure?

    Anyway, thanks again for your comments!

    Chris shared this idea  · 
  5. 7 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)
    An error occurred while saving the comment
    Chris commented  · 

    Would be really cool if you could display the last comment or, at least, have the last comment appear first in the pop-up. Would make it easier to get a quick feel for the status of issues.

Feedback and Knowledge Base