On Wed, 2010-07-07 at 19:25 +0200, david blanchard wrote: > o I create a task, that works. But then I can’t find it anymore, in > any of the tabs (dashboard, past due, open tasks, etc) of my page. I can > only find it by using the email that was sent to me. And I can’t find how to > destroy the task. I did not look in the right place ?
Were your tasks "Essai 1" and "Essai 2" ? They are listed there: http://dev.community.hackit.cx/wiki/User:Da#tab=Open_Tasks To delete the task, you just do like with any wiki page - you click on the task, and use "Delete" when you are logged in. > o The dashboard does not seem to work : I can’t see the tasks due for > the current month, and I can’t change the month that is displayed I can see the task listed there - though it's true, there is an issue with the calendar. The semantic calendar extension seem to have been replaced by another one http://www.mediawiki.org/wiki/Extension:Semantic_Result_Formats - I'll install this one instead, this should probably help to fix the issue. > * The basic question that will help me think about the way we can > track tasks : how much work would it be to have a page that lists all tasks, > with possibility to filter by assignee, status, target, etc. > The idea would be that anyone can add tasks, take them, and it’s easy to > have a view of the current list of tasks that for instance don’t have an > assignee yet. This should be fairly easy to do - for example, showing the list of open tasks within a page can be done by adding the following to any wiki page: {{#ask: [[Category:Task]] [[Status::New||In Progress]] | ?Assigned_to | ?Target_date | sort=Target_date }} Which gives: http://dev.community.hackit.cx/wiki/Test > * Regarding the production pipeline (and not the follow up of tasks in > general), I need to discuss with you and have a clear idea of the workflow > before I can look at the needs for this tool. See the mail I sent yesterday > on the topic, > http://community.hackit.cx/forum/index.php?t=msg&th=3444&goto=8063&#msg_8063 > , penultimate bullet point. > Basically I think it will be interesting to have a page that list the > features we know we will have in next builds n+1, n+2, etc. This comes from > uservoice and discussions on the ml. Then each of these features is a link > towards a page that lists the tasks attached to it (we can use a tag for > this I guess). Though not in this tool yet, we already have this in Launchpad: https://launchpad.net/hackit/+series Then click on alpha1.1 to get the list of features/blueprints. > * This makes me think of another feature that would be very > interesting, either for the generic tracking of tasks or for the production > pipeline. It’s if we can attach tasks to another (father and sons). That > would be useful. This way we can have on the form of the feature task the > overall blueprint, and on the forms of the sons of this task the details of > each task. I did not find a way to attach a task to another though in the > present tool. The idea here is to reduce the number of tools by having if > possible only uservoice and this mediawiki for the workflow. For this, we could simply use project names - you could have a page listing all tasks related to a given project name. And also, a task remains a "normal" wiki page - so you can also add a custom list of tasks like the one I mentioned earlier in the body of a task: http://dev.community.hackit.cx/wiki/Essai_1 Would it do what you want to achieve? Xavier. _______________________________________________ Hackit Bar mailing list - [email protected] Wiki: http://community.hackit.cx/ List: http://community.hackit.cx/ml/ Forum: http://community.hackit.cx/forum/ Ideas: http://community.hackit.cx/ideas/ IRC: irc://irc.freenode.net/#politis
