GTG

Same name should always link to the same task

Bug #339878 reported by fonji
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GTG
Won't Fix
Wishlist
Unassigned

Bug Description

Writing twice or more a "link" to a subtask in a task should link on the same subtask.
I'm not sure that's a really good idea but it just came to my mind... I just thought that if you have a big text as task, you may want to reference a subtask more than once.
Of course you can just type the name in the text but then you'll have to go back in the text and find the appropriate "link" or mess with you windows.

Example :
My new task
blablabla
- test
and
- test 2
or
- test 3
but don't forget to finish
- test
before doing
- test 2
or
- test 3

This will create two "test" subtasks, two "test 2", ... which may be confusing in the main window.
Fortunately the tasks are always ordered by appearance and not by their name, it already avoids some confusion.

Changed in gtg:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Shahar Or (mightyiam) wrote :

I think that the larger picture of this issue would be to make tasks with the same name actually the same tasks.

For example, I many times have multiple tasks which have the same subtask:

    PUT PICTURE ON THE WALL
    @home,@someday
    I have a lovely picture which should be put on the wall. For this I need to
    - Buy 2 inch nails

    INSTALL SHELF IN OFFICE
    @office
    The shelf I made is great! I bet it will look excellent on the wall with all my stuff on it! First I'll need to
    - Buy 2 inch nails

In this example as of 0.1.2, there will be two tasks by the title "Buy 2 inch nails". I think that the wiki-like behavior of identifying an item by it's title should be preferred by most GTG! users.

Many blessings.

Revision history for this message
Bertrand Rousseau (bertrand-rousseau) wrote : Re: [Bug 339878] Re: Ability to "link" multiple times the same subtask

I'm fine with this. However we should find a way to avoid 'collisions'
with existing (for instance, done) tasks. For a common task, we will
rapidly have the same title.

On Thu, Jul 9, 2009 at 7:05 PM, Shahar Or<email address hidden> wrote:
> I think that the larger picture of this issue would be to make tasks
> with the same name actually the same tasks.
>
> For example, I many times have multiple tasks which have the same
> subtask:
>
>    PUT PICTURE ON THE WALL
>    @home,@someday
>    I have a lovely picture which should be put on the wall. For this I need to
>    - Buy 2 inch nails
>
>    INSTALL SHELF IN OFFICE
>    @office
>    The shelf I made is great! I bet it will look excellent on the wall with all my stuff on it! First I'll need to
>    - Buy 2 inch nails
>
> In this example as of 0.1.2, there will be two tasks by the title "Buy 2
> inch nails". I think that the wiki-like behavior of identifying an item
> by it's title should be preferred by most GTG! users.
>
> Many blessings.
>
> --
> Ability to "link" multiple times the same subtask
> https://bugs.launchpad.net/bugs/339878
> You received this bug notification because you are a member of Gtg
> developers, which is the registrant for Getting Things GNOME!.
>
> Status in Getting Things GNOME!: Confirmed
>
> Bug description:
> Writing twice or more a "link" to a subtask in a task should link on the same subtask.
> I'm not sure that's a really good idea but it just came to my mind... I just thought that if you have a big text as task, you may want to reference a subtask more than once.
> Of course you can just type the name in the text but then you'll have to go back in the text and find the appropriate "link" or mess with you windows.
>
> Example :
> My new task
> blablabla
> - test
> and
> - test 2
> or
> - test 3
> but don't forget to finish
> - test
> before doing
> - test 2
> or
> - test 3
>
> This will create two "test" subtasks, two "test 2", ... which may be confusing in the main window.
> Fortunately the tasks are always ordered by appearance and not by their name, it already avoids some confusion.
>

--
Bertrand Rousseau
Place communale 1, 1450 Chastre, Belgium
e-mail : <email address hidden>
tel : +32 485 96 69 86

Revision history for this message
Shahar Or (mightyiam) wrote :

On Tue, Jul 14, 2009 at 1:17 AM, Bertrand
Rousseau<email address hidden> wrote:
> I'm fine with this. However we should find a way to avoid 'collisions'
> with existing (for instance, done) tasks. For a common task, we will
> rapidly have the same title.

Firstly, I think that I very rarely name a new task using an existing name.

Hey - how about we turn it around; for common tasks entered over and
over again, instead of calling them collisions, perhaps we somehow do
acknowledge that they're essentially the same task over again.

Perhaps in this case the data from the old task can be useful for the user.

Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote : Re: Ability to "link" multiple times the same subtask

that's a good idea. When you enter a task which already exist, the task could be reopened (and a line "this task was closed on XXX/XX/2009" could be added)

Changed in gtg:
milestone: none → 0.3
Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

Note : currently, copy/pasting a subtask link to the same subtask and don't create a new one, which is a partial solution to this bug.

Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

As we can actually link multiple times to the same subtask with copy/paste, the remaining bit of this bug is to have "one name == one task".

But, in the backends discussion, jml was strongly against this idea and it seems to make sense.

So, do we want to have one title=one task or not ?

summary: - Ability to "link" multiple times the same subtask
+ Same name should always link to the same task
Changed in gtg:
milestone: 0.3 → none
importance: Medium → Wishlist
status: Confirmed → New
Revision history for this message
fonji (fonji) wrote :

Well, before saying anything, I'd like an example where it makes sense to have multiple subtasks with the same name.
I think it creates confusion in the tasks list too.

Revision history for this message
Luca Invernizzi (invernizzi) wrote :

The problem is simple:
if we adopt the paradigm "one title = one task" we'll have compatibility issues with all the backends that do not use that paradigm.
I can name two: remember the milk and google tasks.
If we don't adopt that, the user is free to decide that that paradigm makes sense for him, and "manually" follow that.

 @fonji:
example of a student task list::
- prepare for test X
    - study chapter 3
    - make some exercises

- prepare for test Y
    - study chapter 3
    - make some exercises

or:

- organize a super mega party
   - buy sugar
   - buy tequila
   - buy lemon

- buy something for breakfast
  - buy sugar
  - buy milk
  - buy cheerios

I don't think it creates confusion, it does only if the gtg user is confused :-D

So, I'm against that paradigm.

Revision history for this message
fonji (fonji) wrote :

I agree with you, this makes sense. Only because they are subtasks of different tasks.
You have no example of a task with two subtasks with the same name in the same task, as given in the bug report.

Example:
- go to the mall
  - buy sugar
  - buy tequila
  - buy lemon
  - buy sugar
  - buy milk
  - buy cheerios
- do something else
  - buy sugar

The "go to the mall" task should have only one "buy sugar" subtask, IMO. But the "buy sugar" subtask from "do something else" should be another subtask, as you suggest.

Hum... Am I understandable?

Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

Given that we can now have the same subtask linked multiple times in different tasks.

Given that jml, invernizzi and myself are against the same name paradigm.

I close that bug as won't fix.

What might be interesting is to have a way to easily add an existing task as subtask but this is another bug and will requires some UI thought.

Changed in gtg:
status: New → Won't Fix
Revision history for this message
Micah Gersten (micahg) wrote : Re: [Bug 339878] Re: Same name should always link to the same task

I have a real use case.

Package Sunbird for Lucid

Package Enigmail for Lucid

The sub task for both is

Wait/Push for Mozilla Upstream to produce thunderbird-dev files

This is not 2 instances as this subtask is done once and then
either/both of the tasks can proceed.

So, maybe this shouldn't be same name, same task, but maybe some way to
have common sub tasks...possibly link subtask to other task? Should I
file a new bug for that?

Thanks,
Micah

On 01/07/2010 08:42 AM, Lionel Dricot wrote:
> Given that we can now have the same subtask linked multiple times in
> different tasks.
>
> Given that jml, invernizzi and myself are against the same name
> paradigm.
>
> I close that bug as won't fix.
>
> What might be interesting is to have a way to easily add an existing
> task as subtask but this is another bug and will requires some UI
> thought.
>
>
> ** Changed in: gtg
> Status: New => Won't Fix
>
>

Revision history for this message
Bertrand Rousseau (bertrand-rousseau) wrote :

I think we'll take a safer route by not having "one title == one
task". In a user perspective, a nice workaround to be able to link to
the very same task when typing its title would be to use some kinf of
autocompletion UI (picture a dropdown with a list of matching title,
and some more information, like tags, first line of text, etc.). This
is not going to be easy to implement, but I think it's the right way
to do it.

On Thu, Jan 7, 2010 at 7:33 PM, Micah Gersten
<email address hidden> wrote:
> I have a real use case.
>
> Package Sunbird for Lucid
>
> Package Enigmail for Lucid
>
> The sub task for both is
>
> Wait/Push for Mozilla Upstream to produce thunderbird-dev files
>
> This is not 2 instances as this subtask is done once and then
> either/both of the tasks can proceed.
>
> So, maybe this shouldn't be same name, same task, but maybe some way to
> have common sub tasks...possibly link subtask to other task?  Should I
> file a new bug for that?
>
> Thanks,
> Micah
>
> On 01/07/2010 08:42 AM, Lionel Dricot wrote:
>> Given that we can now have the same subtask linked multiple times in
>> different tasks.
>>
>> Given that jml, invernizzi and myself are against the same name
>> paradigm.
>>
>> I close that bug as won't fix.
>>
>> What might be interesting is to have a way to easily add an existing
>> task as subtask but this is another bug and will requires some UI
>> thought.
>>
>>
>> ** Changed in: gtg
>>         Status: New =>  Won't Fix
>>
>>
>
> --
> Same name should always link to the same task
> https://bugs.launchpad.net/bugs/339878
> You received this bug notification because you are subscribed to Getting
> Things GNOME!.
>

--
Bertrand Rousseau

Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

Micah > it's already possible but there's no good ui for it.

1) create a subtask in a given task
2) select the subtask (including the arrow)
3) copy it
4) paste it in another task

The same task is linked in both tasks now.

Revision history for this message
Micah Gersten (micahg) wrote :

Doesn't work in 0.2
I can't copy and paste the task.
If I highlight and middle click in the new task, it doesn't link it.

On 01/07/2010 03:17 PM, Lionel Dricot wrote:
> Micah> it's already possible but there's no good ui for it.
>
> 1) create a subtask in a given task
> 2) select the subtask (including the arrow)
> 3) copy it
> 4) paste it in another task
>
>
> The same task is linked in both tasks now.
>
>

Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

It might only work with the real copy/paste. I don't know if we could
add support for the middle click too (or if it's only a X clipboard)

Le jeudi 07 janvier 2010 à 21:45 +0000, Micah Gersten a écrit :
> Doesn't work in 0.2
> I can't copy and paste the task.
> If I highlight and middle click in the new task, it doesn't link it.
>
> On 01/07/2010 03:17 PM, Lionel Dricot wrote:
> > Micah> it's already possible but there's no good ui for it.
> >
> > 1) create a subtask in a given task
> > 2) select the subtask (including the arrow)
> > 3) copy it
> > 4) paste it in another task
> >
> >
> > The same task is linked in both tasks now.
> >
> >
>

Revision history for this message
Micah Gersten (micahg) wrote :

GTG Copy and Paste doesn't seem to work. Should I file a new bug?

On 01/07/2010 04:04 PM, Lionel Dricot wrote:
> It might only work with the real copy/paste. I don't know if we could
> add support for the middle click too (or if it's only a X clipboard)
>
> Le jeudi 07 janvier 2010 à 21:45 +0000, Micah Gersten a écrit :
>
>> Doesn't work in 0.2
>> I can't copy and paste the task.
>> If I highlight and middle click in the new task, it doesn't link it.
>>
>> On 01/07/2010 03:17 PM, Lionel Dricot wrote:
>>
>>> Micah> it's already possible but there's no good ui for it.
>>>
>>> 1) create a subtask in a given task
>>> 2) select the subtask (including the arrow)
>>> 3) copy it
>>> 4) paste it in another task
>>>
>>>
>>> The same task is linked in both tasks now.
>>>
>>>
>>>
>>
>

Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

It doesn't work for the last line of a task. It's a known bug, already
fixed in trunk.

Le jeudi 07 janvier 2010 à 22:13 +0000, Micah Gersten a écrit :
> GTG Copy and Paste doesn't seem to work. Should I file a new bug?
>
> On 01/07/2010 04:04 PM, Lionel Dricot wrote:
> > It might only work with the real copy/paste. I don't know if we could
> > add support for the middle click too (or if it's only a X clipboard)
> >
> > Le jeudi 07 janvier 2010 à 21:45 +0000, Micah Gersten a écrit :
> >
> >> Doesn't work in 0.2
> >> I can't copy and paste the task.
> >> If I highlight and middle click in the new task, it doesn't link it.
> >>
> >> On 01/07/2010 03:17 PM, Lionel Dricot wrote:
> >>
> >>> Micah> it's already possible but there's no good ui for it.
> >>>
> >>> 1) create a subtask in a given task
> >>> 2) select the subtask (including the arrow)
> >>> 3) copy it
> >>> 4) paste it in another task
> >>>
> >>>
> >>> The same task is linked in both tasks now.
> >>>
> >>>
> >>>
> >>
> >
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.