Open nelinnemann opened 11 years ago
I don't think jobsworth is the right place for this. We already have todo items as lightweight tasks within a task. But any wiki functionality is secondary in jobsworth.
Can you sketch out wireframes of your idea?
Well in our company (about 18000 employees) we have project management software, but they are all either too advanced and cumbersome to use or too simple aka. the Confluence tasks.
The problem with being too advanced means that everyone hates to use the software and neglects to bill correct times to the plan.
The problem with too simple is that it is impossible to do any time-tracking and project billing.
Thats where I think jobsworth could have an real advantage, niche, by being simple to use for regular users, but also more advanced for the hardcore planners.
Keep in mind that people hate to do stuff they shouldn't need to with the right software.
Which is how we ended up writing jobsworth... Jira is nice but was missing some things and was too slow and complex for other things. Bootcamp and friends are easy to use, but too simplistic.
So the test for adding anything to jobsworth is: will it make the UI more complex? If so, it needs a really good reason to be there. I don't really understand how your lightweight todo items interact with real tasks. Is it just a simple UI to create tasks quickly? Or is it something else?
Our simplest UI to create tasks is by sending emails to jobsworth. But I've always wanted to do an XMPP integration as well.
No its no even an UI.
In my mind it is a wiki page where you have a macro called "tasklist" or "todolist".
something like this
########
Find the root cause of product failure
@user1 @user2 @user3
(insert macro tasklist) @user1 do the litterature study @user3 contact @specialist regarding the issue
#################
The tasklist macro then (in the background) creates a task in the project (because the wiki belongs to that project). If using the @user mentioning it gets assigned to that user and he can start working on it
If the @user mention is not used the task should be created with no user assigned.
actually this "wiki" on git also used the @user as I can mention the users on this page eg @ari
Let's forget the wiki for a moment. it seems what you are asking for is a big text box where you can quickly create tasks by typing special syntax. Username, task title, etc Whether that's inside the wiki or not isn't the most important part.
I like the idea and it is similar to my concept of doing it over XMPP. Imagine sending a chat message:
Jobsworth create Buy cornflakes tomorrow
And we could decorate it just the way github does with # and @ symbols to link other tasks or people.
yes that would be just as good.
Its just that when in meetings you don't want to deal with spending 1-3min creating each task.
Having simple tasks similar to the stuff Confluence uses is a real time saver eg. when taking meeting notes.
https://confluence.atlassian.com/display/DOC/Managing+Tasks+in+Confluence
The real benefit is then @user mentioning Confluence is using.
So making a tasklist in the wiki and using @user its possible to directly assign that task/todo to the correct user and when the user marks it as complete it gets reflected on the wiki.
This is a real time saver when having formal/informal meetings to track who said what and who does what.
When the task is created the user/planner can then go into the task and define the task more precisely, but it would be a real time saver in meetings.