ThinkingRock Forum

In v. 1.2.3 I simply created a project called "Single Actions" in my Projects view. Just upgraded to v. 2.0.1 and I still have to create a project item called Single Actions to work with it--i.e.--to be able to print it with a Project Report.

What advantage is there to put single actions in that seperate tab view ?

_________________
Bradco

Following up to my initial post: How do I get rid of the 2 tab views: Single Action and Templates ?? I do see the "Undock Window" option- Alt-View-D. However, this option does not persist beyond the current session. I also, see that tabs can be physically re-arranged, so that only the tabs the user wants can be grouped together--i.e.--projects & future projects . However, again, re-arranging the order of the tabs DOES NOT PERSIST beyond the current session. Could you please introduce OPTIONS that allow persistent choice about these views. Thanks

_________________
Bradco

A single actions section will be added to project reports soon.

_________________
Claire
ThinkingRock Analyst and Tester

Is there a way to print the Single Actions view as a stand-alone report ?

I'm just wondering what a user can do with this tab view, other than collect and view Single Actions ? Eventually have to cut & paste into another view to do something with, like print out . . . ? How are others using this view ?

_________________
Bradco

Single actions view is pretty straight forward I think: To be able to handle actions that are not tied to a project we have the concept of 'single actions'. Now, to review your single actions they need to have a place in the system where you can find them together and the 'single actions tab' is an elegant solution. For example, some other GTD-apps need you to create a project to hold single actions but that project is just 'somewhere' between your other projects. THEN you need to give it a specific name (like start it's name with a dot) to make it float alphabetically to the top of your project list.

TR's implementation is mighty fine, the only thing lacking is a specific report for single actions and that is being worked on.

Would you prefer a separate report or a section added at the end of the project report?

_________________
Claire
ThinkingRock Analyst and Tester

I vote for a separate report for single actions.

Single Actions was originally part of the Projects view in v 1.2.3. It provides a concise, at-a-glance view of projects (which are made up of actions) and also single actions, which are projectless. Should be all together as a view and as a print out (one view/print out for simplicity and comprehensiveness). Let's consider: What is it about an action that has no project (Single Action), that it should be entirely separate and unviewable and unprintable, except by itself ??

_________________
Bradco

It's not about keeping single actions separate from projects, it's about keeping the projects view as uncluttered as possible. If you have a large amount of projects to manage (I manage both my personal life, personal development AND all of my company and client projects in TR) then the project view becomes close to unbearable already without the whole load of single actions added to it.

Of course I have no idea where you are coming from (so don't take this as personal criticism), but I'll take it you have less then 50 projects overal (including future) and maybe a same amount of single actions, because in that case I can see your point. There are probably many users who have even less and having just a few single actions in one tab and a few projects in another tab might seem counter productive.

Me on the other hand (and I know of several users like me), I have currently around 70 active projects and over 170 in future projects. Most active projects contain between 3 and 15 sub-projects, in some cased with hundreds of tasks across them in one project alone. My single action list almost never dips below a 100 active tasks. Dump all this into one view and it becomes a nightmare.

I see your point: Then, the issue of either a combined Single Actions section--with Projects--or a separate view/print, should naturally be set as a PERSISTENT OPTION. The program needs to have the flexibility to incorporate different needs. In as much as you and others may wish separate views, just as many (like I) may want combined views-- this is "simplicity" to me

_________________
Bradco

I think having just one tree on a single tab would be the easiest conceptually and the easiest to process. After all clicking on a tab is little different from expanding a node on a tree.

I would then like to have the ability to create a complex (Boolean logic) selection criteria. To make this easy for users it could be based on "print all open nodes in the tree subject to the tab's filters." So what you see in the actions tab is what gets printed. Since I print very little the view to PDF seems ideal. I just want to extend that principle.

For example if you had opened the "single action" tree node you would get single actions in your report, if not, you wouldn't. Similarly if you closed all project nodes and just left the single actions node and one project open you would get just that one project with your single actions.

This concept would also allow you so specify whether you wanted your single actions at the top, bottom, or even, the middle of your reports.

You may want several print options for large paper and pocket mod paper but it should be easy to print using a numbering system or indent system to show the node hierarchy e.g.
01 XYZ.com
01.01 XYZ's outhouse building
01.02 XYZ's outhouse interior plumbing
01.02.01 XYZ's outhouse sauna
01.02,02 XYZ's outhouse slide
01.03 Demolition of work area
02 ABC Corp
....
170 Single actions

Under each heading would be the data in the format of the existing Action Screen to PDF view. With column headings noted at the top of each page.

Agreed, and probably not that difficult to accomplish, as Jeremy already stated that he wants ALL the project data (current, future, etc.) internaly in one place (one data-tree as he called it).