Propel 2.0

It has been long over due. For those of you who have been waiting, thank you. To any new users who find this, I hope you enjoy. I planned to include more features than those of which are being released, but in lieu of some bugs introduced with WordPress 3.3 which render the 1.x branch of Propel useless, I decided it was better to hide some partially implemented 2.0 features than to fix the bugs in 1.7 or postpone the release of 2.0. Before you upgrade to from 1.7 to 2.0, it is strongly recommend you take a full backup of your database. The major changes being released are largely internal.

New Features (2.0)

  • Propel 1.7 moved to custom post types. Propel 2.0 now takes full advantage of the default UI functionality and used the interface provided by custom post types. This allows for better integration with WordPress as a whole, and Propel now plays well with other plugins that modify custom post types.
  • In 1.7 project and task meta were stored as a single key as a serialized array. This made filtering data impossible. Each piece of data is now stored as an individual metakey (documentation will be provided on how to take advantage of this). This is why you will receive a database update notice when you upgrade from Propel 1.7 to 2.0.
  • Changed the priority from 1-10 to use Low, Medium, and High instead. After the upgrade, any tasks previously with a priority of 1-3 will be low priority. Tasks with a priority with 4-7 will have a medium priority and tasks with a priority 8-10 will have a high priority.
  • Changed progress from intervals of one to intervals of five. Upon upgrading, your previous tasks progress will be rounded to the nearest five.
  • Removed the shortcode for a frontend display (sorry! I know some people used this, but it is kind of unnecessary. I will explain how to display your projects and tasks in the frontend in another post later)
  • Ability to categorize tasks
  • A better interface for adding terms to tasks
  • Ability to assign projects to clients
  • Ability to globally turn on/off start date, end date, project progress, and project client (keep in mind, using the “Screen Options” at the top of your WordPress admin pages, you can hide columns and widgets).
  • Task “type” taxonomy – giving you the ability to classify tasks as bugs or features.

Partially Implemented / Hidden Features (2.1 ETA ~1.5 months)

  • A taxonomy to reflect the “state” of a task –  Not Started, Started, Completed, Delivered, etc…
  • Ability to add custom task “types”
  • Better filtering (if you have a lot of tasks, it is very hard to manage the tasks via the All Tasks page)
  • Roles and capabilities. In its current release, everyone can see all the tasks. The goal here is to create two “roles” – Project Manager and Developer. Developers would only see tasks assigned to them, while project managers would be able to see all tasks.
  • Email notifications when a user is assigned a task, a task is updated, or a comment is made on a task.

Planned Features (2.2+)

  • A full featured theme (this will likely be a paid add-on)
  • GitHub post-receive hook endpoint (add comments to tasks and complete tasks when you commit to github)
  • Integration with WP-Invoice (need help from the WP-Invoice guys for this)
  • Ability to group tasks into “task lists” or “milestones” or “sprints” or “iterations” or whatever project management paradigm calls it.
  • Gantt Chart
  • Burn Down Chart
  • Other charts that I don’t know about
  • Features you request

Related posts:

  1. Propel Information regarding the propel project can be found at http://www.johnciacia.com/propel/...
  2. Creating a custom style for Propel The Propel front end currently relies on jQuery to create a tabbed interface for your projects. This brings along with...
  3. Propel Update 1.5.4 Optimized JavaScript includes Fixed jQuery conflicts Improved the “Propel” / “Info” page by adding widgets / meta-boxes The next update...

Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Notify me of followup comments via e-mail. You can also subscribe without commenting.


17 Responses to “Propel 2.0”

  1. Josef Ulander

    Hi, when I click at the migration tool link I just arrive at a blank admin page, there is nothing ot click on. What am I missing?

    Josef

    Reply |

  2. Flick

    Hi John
    Thanks very much for creating Propel. I have been experimenting with some project management plugins over the past few hours and Propel is definitely what I had in mind!
    You mentioned that the 2.1 road map only includes 2 roles – the project manager and the developer. How about an extra role for the client? In this instance I would be both the project manager and the developer, but I would like clients to be able to add tasks (or maybe they can already – I just need to work out how) – perhaps you wouldn’t mind clarifying this for me?

    Many thanks again! :)

    Reply |

  3. Tschai

    Please add the following minor change in the following minor update:
    The names of the tasks and projects in the Dashboard Project Overview should be an URL to the corresponding tasks/projects…this is a major flaw.

    And maybe add the prio/progress and author of the project behind the progress bar also?

    Thanks again and regards.

    Reply |

  4. Jose Rivera

    Been testing out various task/project management WP plugins for a few months now. I’m glad I stumbled across Propel when I did (congrats on version 2.0!), as it fits my needs almost perfectly.

    I look forward to future releases of this project, and perhaps even bother you about it once I really get into playing with it. :)

    Reply |

  5. Tschai

    It’s true that I can able to see the (overall) progress of a project, but It would be great if I could at least see the progress of ALL THE PROJECTS with their task in the over

    Well ,the previous overview is simply perfect: from a graphical representation to the fact it could be accessible from the frond end (for others than the admin).

    I can imagine, that that’s time consuming.
    A simple overview/report of all projects+tasks or specific project+tasks available for other users in it’s most spartan form should be a minimum.

    Reply |

    • Tschai

      Doh!
      Posted before cleaning things up…but the request should be kinda clear, anyway.

      Reply |

    • John

      I’ve added a “Project Overview” dashboard widget in 2.0.3. Due to some WordPress UI constraints, it can’t go where it was previously.

      Reply |

      • Tschai

        Just saw the project overview on the dashboard: it’s perfect!
        What a swift and great service.

        Up towards the next releases!

        Reply |

  6. Tschai

    Congrats with the new version…

    However I’m not getting past the ‘Propel has changed its database structure. To continue using this plugin, you must first use our migration tool’ warning: although I’ve deinstalled the prev version.
    And the migration tool does not link anywhere aka ‘page=propel_migrate_tool’ show only the above message.

    Or do I need to drop the v1.7 tables manually?

    Hope you can fix that.

    Regards.

    Reply |

    • John

      Taking a look. Give me a few.

      Reply |

    • John

      Can you wp_options table can you look for an “option_name” of “PROPEL_DBVERSION” and if it exists, can you please tell me the option_value?

      Reply |

    • John

      ok, so your problem was that the PROPEL_DBVERSION didn’t exist because the activation hook wasn’t firing. You can either add the key and set its value to 1.6 manually or install 2.0.1 and deactivate / reactivate.

      Reply |

      • Tschai

        I’ve fully deleted the installationa nd uploade the latest version (2.0.1) and my whole site crashed, with the following errors:

        Warning: require_once(__DIR__/functions.php) [function.require-once]: failed to open stream: No such file or directory in …l/wp-content/plugins/propel/propel.php on line 57

        Fatal error: require_once() [function.require]: Failed opening required ‘__DIR__/functions.php’ (include_path=’.:/usr/local/lib/php’) in …l/wp-content/plugins/propel/propel.php on line 57

        I’m just letting know.
        I’ve now deleted theplugin and will see if I can make it work on localhost.

        To be continued.

        Reply |

        • John

          Any luck on this? I’ve tried several times and I’m unable to replicate this issue.

          Reply |

          • Tschai

            It’s working perfectly on localhost; so it must have been be on the online-site;will let know if I get that working too.

            I’m missing an graphical overview like the prev version: http://www.johnciacia.com/wp-content/uploads/2009/08/overview.png

            Is that still possible? That makes this plugin realy stand out.

            Thanks for the swift replies!

            |

          • John

            That particular graphical overview was removed (in version 1.6 maybe even earlier), in favor of moving toward a more complete frontend (which wasn’t included in this release due to time restraints). If you edit the project, there are widgets that give you the overview. What is it that you like about that particular graphical overview? Is it the location (on the edit.php screen vs. the post.php screen) or is it the progress bars? This is largely a user directed project. I can certainly add it back.

            |

        • John

          Ahhhh, this issue should be resolved in 2.0.2. It was slight oversight on my part. I was using PHP 5.3 specific code ( using __DIR__ ) and your production site is probably running PHP 5.2.x

          Reply |