Quick edit/create functionality for tasks




  • Avatar
    Suzie Prince

    Hey Chris

    There is currently no "quick edit" on card properties on the tree view or anywhere. We have considered some inline edit functionality but at the moment we are not sure whether this will apply to card properties.

    One thing that you might find useful, and our team uses something similar, is to create a transition to add an estimate to a task card. You could call it something like "add estimate to task" and make it apply to cards of type task that have an estimate of (not set). If you set this transition as "user input required" on the estimate property when it is executed the user will be required to add an estimate. As transitions appear on card pop ups you will be able to execute this transition and add an estimate for a card directly from the tree view. If you want to know more about transitions take a look here.

    I hope this helps.

    - Suzie

  • Avatar
    Chris Leon

    Interesting, so this ends up being actually the same workflow as the other post I had about having 'required' card properties at card creation time.

    This strikes me as an ok solution for the two use cases...  Only problem with it is that it forces some users to have another couple of views/reports to their things to be paying attention to, in this case 'tasks without estimates set', where what I'd sort of like to have is a view per usage.

    In this case, there would be a tasking view, preferably a card tree.  At first, it's one level for all the stories that we're thinking about doing in the iteration.  You use the quick add to throw on cards as people churn out the general outlines of the tasks involved in the stories, then after there's general agreement that we know what needs to get done, we put on some estimates.  Having quick edit means you don't need to switch views to get that done, and it's the ONLY thing that would require the view switch.

    I'd even be happy with the quick edit being in the card pop up view, as long as I don't have to go to the full editor, and can see the other cards in the story while I'm editing.

  • Avatar
    Michael Decleene

    Not sure if this will work in your situation, but I've solved similar problems with something like the following:

    Set up a view with an appropriate filter (e.g. Planning-User Story is XXX) and "Group by" Estimate.  Show all lanes.  Now you can quickly drag and drop cards into the appropriate lane to set the estimate.  Quick, easy, and visually appealing.

    This only works if the property you're trying to set is restricted to a fixed set of values (e.g. can't be "any number").  I use this setup to run story estimation sessions, where we're usually picking between 1, 2, 4, 8, 16, and "More than 16" as options.  This may be a deal breaker for task estimates (though I'd argue on most projects restricting task estimates to a set like "1hr, 2 hr, 4hr, 8hr, 12hr, 16hr, 24hr, too big" isn't unreasonable). 

    If this works for you, just make the view a favorite, and edit the story number each time you do a tasking session.  Or just set the filter to show you everything where Task Estimate is "Not Set" (though this has the drawback that the cards disappear once you drag them into a lane).

  • Avatar
    Chris Leon

    Good suggestion!  Of course, I think so cause that's what I initially setup.  ;)

    I didn't really like it though, cause I wanted to have filter as iteration=current iteration, and just show tasks, cause that's what the dev team estimates on (as opposed to stories).  So the grid showed all my tasks, with their names, but no immediate view on what story they were part of, and no ability to do a sort based on story which would've been pretty good too.

    I could get around that by filtering not just on iteration, but also by story, and just flip through the stories in the iteration, but I ended up deciding that I prefer the tree view to that.

Please sign in to leave a comment.