atinypixel / kindmanageapp Goto Github PK

1. Description

Milestones allow projects to scope any entry to a specific time-line. Whether you’re attaching notes, tasks, uploads or issues, yourself and your team can always stay informed about past and upcoming milestones.

1. Description

Project entries can belong to any number of workspaces. Workspaces provide a way to organize project entries in a different context. In short, workspaces provide a way to provide contexts for your ENTIRE project management world, not just for a single project.

1. Use Cases

Teams: I have a team of designers working across multiple projects. I would create a workspace that I’d simply use to gather all design related entries from various projects.

Freelancers: Project management can often be too open. Use a workspace to only gather the information you feel is pertinent to you client or other freelancers you’re working with. You could then just set a user to follow that workspace and nothing else.

1. Specifics

A workspace can be global or scoped under a single project Workspaces scoped under a single project can exist with the same name globally or under a different project, but not in the same project.

More use cases soon

1. Description

The queue will contain what is considered the most critical/important entries in a given project. Basically these are things that upon entering a project, you are expected and should notice first and act upon. Think of it as this: “Yes there are these other project entries, but focus on these instead for now”.

Implement an option in workspaces that allow the user to decide whether or not it can be scoped by a project. This allow workspaces to exist exclusively unto themselves disallowing creation of the same workspace in a project.

UPDATE: Also, allow the deletion of workspaces by account owners.

I'm realizing that the design of Kindmanage is starting to show some serious signs of suckage. Currently, posting a note or task means that you're working with a single Entry model which use or doesn't use fields based on the entry type. It works, but the design will be difficult to scale in lieu of new features and functionality. Additionally, the expense on the database is far too great.

Going with authlogic on this one. Restful Authentication just seems bloated and sometimes awkward to implement.

Since all users in an account are always accessible from the "people" tab, it would make since to be able to drag users to the current project or workspace.

Currently cannot create or edit projects. The UI for this needs to be out of the way, still giving focus to project entries.

When posting note entries, it’d be nice to have the textarea auto-expand as some notes can get long. Also, consider truncating really long note entries.

I absolutely cannot tolerate OS-native button widgets for html forms. So I'm going to say "fuck you" to IE6 and use some javascript to do buttons a little better.

Workspaces and projects may eventually build up a backlog of entries that may have been previously settled, resolved or completed. This kind of data is considered old and less than useful to a project or workspace moving forward. Archiving project entries allow a project to reach completeness.

Allow account owners to archive project entries. When entries are archived they will no longer show up in workspaces or projects.

FRINGE CASE: Project entries that must always be visible.

Workspaces and projects are competing for primary interaction. Projects need to be private only to account owner.