Try new Dynamictasklist2 macro in the Fluid wiki?
Eli Cochran
eli at media.berkeley.edu
Fri Jan 9 20:19:29 UTC 2009
Awesome!
\Thanks for testing that Allison. I should have looked at it myself
before sending the email out. I appreciate your covering for my moment
of laziness!
- Eli
On Jan 9, 2009, at 11:44 AM, Allison Bloodworth wrote:
> I believe that has been fixed in this newer version we are using.
> The only way I can find to delete tasks is to click on the trashcan
> icon which appears only when you mouse over a task, and you are
> given a confirmation message before the task is deleted.
>
> On Jan 9, 2009, at 11:35 AM, Eli Cochran wrote:
>
>> I have a concern with this feature. When Allison, Daphne and I were
>> playing around with it a couple of days ago, it appeared that it
>> was very easy to delete a task by a slip of the mouse. I haven't
>> had time to look into it further and it maybe that the features are
>> worth the risk.
>>
>> And again, I played with it for all of 2 minutes so I may be
>> mistaken.
>>
>> - Eli
>>
>> On Jan 9, 2009, at 11:16 AM, Justin wrote:
>>
>>> Hello, I have updated the http://wiki.fluidproject.org/display/fluid/Release+Testing+Tasks
>>> page to use the new version of the task list macro. I am noticing
>>> that you sometimes have to refresh the page a couple of times
>>> before the most recent set of tasklists is displayed.
>>>
>>> A handy feature that I have noticed is that you can drag a task
>>> from one list to another.
>>>
>>> - Justin
>>> On 9-Jan-09, at 12:24 PM, Allison Bloodworth wrote:
>>>
>>>> Hi folks,
>>>>
>>>> Since there weren't any objections, I activated the
>>>> {dynamictasklist2} macro in the wiki. You can see it in action
>>>> at: http://wiki.fluidproject.org/display/fluid/Date+Picker+Tasks
>>>> and http://wiki.fluidproject.org/display/fluid/Release+Testing+Tasks
>>>> .
>>>>
>>>> You can see more options for information you can assign to each
>>>> task (e.g. priority and assigned to) by opening the disclosure
>>>> triangle to the left of each task. You do need to use someone's
>>>> confluence user ID when assigning them to a task, but you can use
>>>> the search functionality next to the field to find it.
>>>>
>>>> Erin and I did notice a bug in that task information can
>>>> disappear momentarily if two people are editing the same task.
>>>> However, if you simply refresh the page the task information
>>>> should return (it was for us). I did just upgrade to a newer
>>>> version of this macro so perhaps that problem will go away now.
>>>> If you run into any major bugs with this macro, please let the
>>>> list know.
>>>>
>>>> I noticed a few other outdated -- e.g. plugin repository,
>>>> blogging, chart, content formatting, contributors, table, table
>>>> of contents, web-dav, etc. -- Plug-ins in the Plugin Repository
>>>> and upgraded them too, so you may see improved performance in
>>>> other functionality as well. When we upgrade Confluence to a
>>>> newer version, I will upgrade the {dynamictasklist2} macro further.
>>>>
>>>> Cheers,
>>>> Allison
>>>>
>>>> On Jan 7, 2009, at 9:02 AM, Justin wrote:
>>>>
>>>>> I'd be happy to use an improved version of the task list. I find
>>>>> the current one quite limiting at times.
>>>>>
>>>>> - Justin
>>>>> On 7-Jan-09, at 11:45 AM, Allison Bloodworth wrote:
>>>>>
>>>>>> Hi there,
>>>>>>
>>>>>> Yesterday when Erin and I were creating a task list in
>>>>>> Confluence (http://wiki.fluidproject.org/display/fluid/Date+Picker+Tasks
>>>>>> ) to manage some finer grained tasks that we didn't want to put
>>>>>> in JIRA. I noticed that on our list and Jacob's task list (http://wiki.fluidproject.org/display/fluid/Release+Testing+Tasks
>>>>>> ) we are using an older version of the {dynamictasklist} macro,
>>>>>> which unfortunately doesn't have the ability to assign people
>>>>>> to tasks until they complete them (which is a feature we were
>>>>>> looking for).
>>>>>>
>>>>>> I found information on {dynamictasklist}-2 macro: http://confluence.atlassian.com/display/CONFEXT/Confluence+Dynamic+Tasklist+2
>>>>>> , which we actually already have installed. To activate it, we
>>>>>> need to disable the "Dynamic Task List Macros" (which is what
>>>>>> is creating our dynamictasklists now) in the Confluence Plug-in
>>>>>> as it is overriding {dynamictasklist}-2 right now. I tried this
>>>>>> last night and things seemed to work OK, though I did notice a
>>>>>> bug in the {dynamictasklist}-2 at one point (which Daphne & Eli
>>>>>> didn't encounter) where an error message would come up that I
>>>>>> couldn't clear, and ended up having to force-quit Firefox.
>>>>>>
>>>>>> However, I think {dynamictasklist}-2 is worth trying as it has
>>>>>> a ton of really great features, such as:
>>>>>>
>>>>>> inline editing of task descriptions
>>>>>> ability to assign people to tasks before they complete them
>>>>>> drag and drop reordering of tasks
>>>>>> ability to assign priority to tasks
>>>>>> documentation of the date the task was created
>>>>>> ability to lock tasks
>>>>>> ability to sort tasks by the taskname, the assignee, the
>>>>>> priority and completed date
>>>>>> "One of the benefits of Confluence Dynamic Tasklist 2 over
>>>>>> previous task lists is that all data is stored in the page.
>>>>>> Most people will find it easier to edit the tasklist using the
>>>>>> web-interface, but if you want to edit or even create the
>>>>>> tasklist directly, you can do so by editing the page itself.
>>>>>> You can see an example of the tasklist wiki-markup below."
>>>>>>
>>>>>> Finally, it is possible to go back and forth from the old
>>>>>> {dynamictasklist} macro to the new one. From the new macro's
>>>>>> info page:
>>>>>>
>>>>>> "Confluence has shipped with older tasklist macros:
>>>>>> {dynamictasklist1} and {tasklist}, This plugin is designed to
>>>>>> replace those macros. In order for it to work, the older
>>>>>> tasklist macros must be disabled. You can disable the older
>>>>>> "Dynamic Plugin Macros" from the Plugin Manager (Administration
>>>>>> -> Plugins). Once the older tasklists are disabled:
>>>>>>
>>>>>> * When someone views a page containing an older version of
>>>>>> the tasklist, the display will show the new format but the page
>>>>>> will not be updated.
>>>>>> * On first edit of the tasklist from the UI, the data will
>>>>>> be converted to the new format.
>>>>>>
>>>>>> The data in the old format is not harmed. Should you wish to
>>>>>> revert to the older macro, you must 1) renable the old macros,
>>>>>> and 2) revert any page that has been automatically modified
>>>>>> (that is, any page containing a tasklist that has been
>>>>>> modified) to the earlier version."
>>>>>>
>>>>>> What do folks think--would it be OK to give they new
>>>>>> dynamictasklist2 macro a try and see how it works for us?
>>>>>>
>>>>>> Cheers,
>>>>>> Allison
>>>>>>
>>>>>> Allison Bloodworth
>>>>>> Senior User Interaction Designer
>>>>>> Educational Technology Services
>>>>>> University of California, Berkeley
>>>>>> (415) 377-8243
>>>>>> abloodworth at berkeley.edu
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________________
>>>>>> fluid-work mailing list - fluid-work at fluidproject.org
>>>>>> To unsubscribe, change settings or access archives,
>>>>>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>>>>
>>>>
>>>> Allison Bloodworth
>>>> Senior User Interaction Designer
>>>> Educational Technology Services
>>>> University of California, Berkeley
>>>> (415) 377-8243
>>>> abloodworth at berkeley.edu
>>>>
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________________
>>> fluid-work mailing list - fluid-work at fluidproject.org
>>> To unsubscribe, change settings or access archives,
>>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>
>> . . . . . . . . . . . . . . . . . . .
>>
>> Eli Cochran
>> user interaction developer
>> ETS, UC Berkeley
>>
>>
>
> Allison Bloodworth
> Senior User Interaction Designer
> Educational Technology Services
> University of California, Berkeley
> (415) 377-8243
> abloodworth at berkeley.edu
>
>
>
>
. . . . . . . . . . . . . . . . . . .
Eli Cochran
user interaction developer
ETS, UC Berkeley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090109/35a74aab/attachment.html>