Gantt Predecessors ID in Task Information

[Dev_Coppelis]

Hi,

In task information popup, the ID of predecessors is wrong.

See attached example (done on you demo web site):
In taks information , predecessor ID for "Investigate" is 11

2.PNG (62.34 KiB) Viewed 2759 times

In the gannt, this task ID is 3

S1.PNG (135.14 KiB) Viewed 2759 times

[pmiklashevich]

Hello,

'#' is a Sequence column - A "calculated" column which displays the sequential position of the task in the project.

Please add these 2 columns to the sample to see the difference:

        {
            xtype     : 'sequencecolumn',
            width     : 50
        },
        {
            text      : 'ID',
            dataIndex : 'Id',
            width     : 50
        },

[Dev_Coppelis]

Hi,
Thanks, yes I understand the difference between the 2 fields
The issue is that this makes the end user view cofused?
In the gannt view the predecessor is 3 but when he opens the task information the same is displayed 11. do you understand what I mean?

Is is possible to display the sequencecolumn in the task information ?

[pmiklashevich]

There are 2 configs called useSequenceNumber: on Dependency column and on DependencyGrid widget.

So there are 2 options how to make IDs look the same:
1. Remove useSequenceNumber flag from the Dependency column, so predecessor will use real task ID:

{
    xtype             : 'predecessorcolumn',
    // useSequenceNumber : true
},

2. Add useSequenceNumber flag to the DependencyGrid widget, so it will show sequence number instead of real task ID:

plugins : [
    {
        ptype : 'gantt_taskeditor',
        dependencyGridConfig : {
            useSequenceNumber : true
        }
    },
    ...
]

[pmiklashevich]

I've just added useSequenceNumber flag to the DependencyGrid in Advanced sample. So it will be fixed in 6.0.4.

[Dev_Coppelis]

Yes really good, End user does not care about real Task ID.
Thanks

[pmiklashevich]

We've just realized that our Task Editor clones the store and doesn't copy all the records into it. But it should. Due to this fact, sequence number could be different from what you can see in the main grid. So we would recommend to abstain from using sequence numbers until https://app.assembla.com/spaces/bryntum/tickets/6846 is done. I commented out useSequenceNumber in the Advanced sample.