Forum

  • If you are new to these Forums, please take a moment to register using the fields above.
Announcement Announcement Module
Collapse
No announcement yet.
Automatically converting projects to subprojects Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Automatically converting projects to subprojects

    I installed the Outlook Add-in, and I really like the idea of having a subproject level. (Sidebar: This doesn't come close to an outliner program like Bonsai for the ability to create n levels of project hiearchy... BUT, this new version of the Add-in is NICELY integrated with Outlook!)

    My only problem is now I have a long list of projects that should now be classified as subprojects of an existing project. Is there any EZ way to turn a project into a subproject? Otherwise I have to do a TON of manual work to create all new projects and reassign ALL tasks to the new projects.

  • #2
    I emailed Netcenrics last week on this issue.
    In short, there is no way to do this, except to re-build your project tree.
    They have submitted it for future release consideration
    CK

    Comment


    • #3
      Managing projects & subprojects & tasks

      A couple of thoughts that may ease the burden somewhat. The actual projects (which are in effect outlook task items with the category set to project) will need to be renamed, manually. You will also need to manually change one next action for each sub-project by opening the outlook task item (next action) and creating it from the drop down list for sub project (after assigning it to the correct project as needed.)

      Once you've done this for a single next action however, you should be able to use the Active Tasks by sub-project view and drag and drop additional tasks into their correct sub-project grouping.

      This will only be helpful of course if you have projects/sub-projects with more than one next action.

      Comment


      • #4
        As I mentioned in another post, a subproject doesn't get its own task, so if you convert existing projects into sub projects, you loose the ability to add notes to the subprojects (if, like me, you hold the list of actions in the task notes section of the project task, that is)

        Comment


        • #5
          Has this been resolved yet?

          Originally posted by tDot View Post
          I installed the Outlook Add-in, and I really like the idea of having a subproject level. (Sidebar: This doesn't come close to an outliner program like Bonsai for the ability to create n levels of project hiearchy... BUT, this new version of the Add-in is NICELY integrated with Outlook!)

          My only problem is now I have a long list of projects that should now be classified as subprojects of an existing project. Is there any EZ way to turn a project into a subproject? Otherwise I have to do a TON of manual work to create all new projects and reassign ALL tasks to the new projects.
          Does anyone know if this has been resolved yet? I'd also like to have the flexibility to convert existing projects into subprojects as my landscape evolves.

          What's nice about the project/subproject heirarchy is that you can capture e-mails and other supporting information that relates to multiple (sub)projects in one place. For example, I may need to develop and maintain a website (one of those projects that never really gets "done" - it's an area of focus perhaps?), for which I need to launch the website first and then continue to maintain it and develop new material. Some e-mails and notes relate to all of these things (i.e. general website stuff), so my current solution would be to have a project called "Develop and maintain website", and subprojects such as "Launch website" and "Develop new material for website". I can then see all material that relates to "website", or drill down to material that relates to only specific aspects of the website project.

          I've seen a few threads discussing different approaches to this. Does anyone have any more thoughts?

          Comment

          Working...
          X