GUI mockup for action dependencies
This ticket tracks the development of a GUI mockup for displaying/adding action dependencies. See also: http://www.getontracks.org/wiki/ActionDependencies/
!https://www.assembla.com/spaces/tracks-tickets/documents/apneKctUGr3QrXeJe5aVNr/download/project_view_with_dependencies3.png!
Note that there are two possible next actions, which all lack (uncompleted) predecessors. They both have a stylized arrow after the action description, indicating that they have successor actions depending on them.
Hovering over the arrow displays the pending actions in the tool tip:
!https://www.assembla.com/spaces/tracks-tickets/documents/bsTGHAtUGr3RV1eJe5afGb/download/displaying_successors_in_tooltip.png!
Actions that have uncompleted predecessors are displayed in the Deferred/pending section, with Pending status. Hovering over the status indicator displays the predecessors in a similar way:
!https://www.assembla.com/spaces/tracks-tickets/documents/a2l8cAtUGr3R4TeJe5afGb/download/displaying_predecessors_in_tooltip.png!
Completing the "Create GUI proposal" action would cause the "Collect community opinions" to become active, and the "Implement revised GUI proposal" gets one less uncompleted predecessor.
!https://www.assembla.com/spaces/tracks-tickets/documents/djEYZMpZGr3R7feJe5afGb/download/action_form_with_predecessor.png!
The "Depends on" field consists of a Gmail-like multiple values auto completion field. This probably imposes restrictions on using commas in action descriptions.
!http://www.assembla.com/spaces/tracks-tickets/documents/a-PCk8vuqr3OqXeJe5aVNr/download/grip_area.png!
Suggestion for a grip area in front of the description to enable drag and drop creation of dependencies. The cursor is changed into move-style when hovering over the area.
Project page example
!https://www.assembla.com/spaces/tracks-tickets/documents/apneKctUGr3QrXeJe5aVNr/download/project_view_with_dependencies3.png!
Note that there are two possible next actions, which all lack (uncompleted) predecessors. They both have a stylized arrow after the action description, indicating that they have successor actions depending on them.
Hovering over the arrow displays the pending actions in the tool tip:
!https://www.assembla.com/spaces/tracks-tickets/documents/bsTGHAtUGr3RV1eJe5afGb/download/displaying_successors_in_tooltip.png!
Actions that have uncompleted predecessors are displayed in the Deferred/pending section, with Pending status. Hovering over the status indicator displays the predecessors in a similar way:
!https://www.assembla.com/spaces/tracks-tickets/documents/a2l8cAtUGr3R4TeJe5afGb/download/displaying_predecessors_in_tooltip.png!
Completing the "Create GUI proposal" action would cause the "Collect community opinions" to become active, and the "Implement revised GUI proposal" gets one less uncompleted predecessor.
Action input form
!https://www.assembla.com/spaces/tracks-tickets/documents/djEYZMpZGr3R7feJe5afGb/download/action_form_with_predecessor.png!
The "Depends on" field consists of a Gmail-like multiple values auto completion field. This probably imposes restrictions on using commas in action descriptions.
Drag and drop
!http://www.assembla.com/spaces/tracks-tickets/documents/a-PCk8vuqr3OqXeJe5aVNr/download/grip_area.png!
Suggestion for a grip area in front of the description to enable drag and drop creation of dependencies. The cursor is changed into move-style when hovering over the area.
Leave a comment
on 2009-05-13 13:27 *
By bohrax
Resolution set to
Description changed from This ticket tracks the deve... to This ticket tracks the deve...
Resolution set to
Description changed from This ticket tracks the deve... to This ticket tracks the deve...
Changed name from "Predecessor" to "Depends on" as suggested by Reinier.
on 2009-06-01 14:25 *
By bohrax
Resolution set to
Description changed from This ticket tracks the deve... to This ticket tracks the deve...
Status changed from New to Accepted
Work remaining set to 20.0
Resolution set to
Description changed from This ticket tracks the deve... to This ticket tracks the deve...
Status changed from New to Accepted
Work remaining set to 20.0
Updated GUI to reflect implementation on http://wiki.github.com/bohrax/tracks
Not sure how I should be giving feedback on bugs in this development branch, I thought I would start here and go from there. If I need to start a new ticket, let me know.
Here is my bug - If I set up a set of actions with dependencies and marked one done from the mobile view, the next action that should have shown now that the dependency had been completed did not show up as I expected. When I refreshed my mobile home page, the next action was not there still. When I went to my regular browser and went into the project with this set of actions and it showed the one I had marked completed as completed, but action with the dependency was still showing under the "Deferred/pending actions in this project" block instead of the "Actions in this project" block. I imagine this may already be on your plan, but wanted to be sure you were aware of it.
Here is my bug - If I set up a set of actions with dependencies and marked one done from the mobile view, the next action that should have shown now that the dependency had been completed did not show up as I expected. When I refreshed my mobile home page, the next action was not there still. When I went to my regular browser and went into the project with this set of actions and it showed the one I had marked completed as completed, but action with the dependency was still showing under the "Deferred/pending actions in this project" block instead of the "Actions in this project" block. I imagine this may already be on your plan, but wanted to be sure you were aware of it.
Thanks Tim, I haven't began looking at the mobile views yet but I can confirm this to be a bug. Perhaps it is a good idea to start a new "feedback ticket". If "dependencies" are accepted into mainline, we can address each issue in a separate ticket. This way we keep all data here, but don't pollute the issue tracker with unnecessary tickets.
The mobile view is an issue in itself. My suggestion is that we don't add entry/edit and advanced view functionality in the first version. Filtering actionable actions and completing actions should of course work as expected.
The mobile view is an issue in itself. My suggestion is that we don't add entry/edit and advanced view functionality in the first version. Filtering actionable actions and completing actions should of course work as expected.
I'm a bit in doubt about the drag-handle (although I think its a perfect icon!). It could easily be confused with action reordening, where you can put an action above another for whatever reason (priority, actionable, etc.)
Perhaps we should add a 'mode' button or something to the upper-right menu to explicitly enable drag-and-drop for dependencies?
Perhaps we should add a 'mode' button or something to the upper-right menu to explicitly enable drag-and-drop for dependencies?
on 2010-01-17 12:15 *
By epall
Status changed from Accepted to Fixed
Work remaining changed from 20.0 to 0.0
Status changed from Accepted to Fixed
Work remaining changed from 20.0 to 0.0
Feels to me like we're set with dependencies. Great work, Henrik! If anybody wants to see changes to dependencies, please open a new ticket.