Support Forum

[victor]

Hello,

I have a doubt about using a filter to filter subtasks and using it for notify.

In the filter edit sheet there are three zones:
- Attributes zone (first line)
- Task fields zone (from 'Task #' to 'Navigator' row)
- Message parameters zone (from 'View Messages' to 'Message Text' row)

Well, now I am going to check they from two sides : to filter subtasks and to notify.

Filter subtasks

- Attributes zone: Right, no problem.
- Task fields zone: Only tasks that make good all the defined filter conditions in this zone are showed.
- Message parameters zone: Only tasks that have one (or more) message that make good all the defined filter conditions in this zone are showed (and optionally this message are showed too).

Notify filter

- Attributes zone: Every field here (except two) mean that the notification is only for tasks that make good the checked conditions (for example: 'has deadline'). The first and second fields mean:
----- Task/page : Unused
----- Deep search : Unused because notify filter have 'deep search' behavior

- Task fields zone: The notification is only for tasks that (after applied the transition) make good all the defined filter conditions in this zone.

- Message parameters zone: The notification is only for tasks which last message make good all the defined filter conditions in this zone.

Questions

am I right? or maybe is wrong my interpretation for the last zone in the notify filter case?

Anothe possible interpretation could be:

- Message parameters zone: The notification is only for tasks with one (or more) messages that make good all the defined filter conditions in this zone.

Thanks,

[admin]

Questions

am I right? or maybe is wrong my interpretation for the last zone in the notify filter case?

Anothe possible interpretation could be:

- Message parameters zone: The notification is only for tasks with one (or more) messages that make good all the defined filter conditions in this zone.

In message paramters zone you receive all messages. Your filter settings affect only subtasks zone, this is useful for filter subscription.

Please also find following (from http://www.trackstudio.com/documentatio ... ation.html):

---
If the task has any subtasks, the list of subtasks is displayed according to the filtering conditions. Note that such parameters as deep search or view messages are not used to determine the necessity of sending a notification, though they are used to format the e-mail notification. For example, if a filter used for e-mail notification has the deep search option on, the e-mail notification will include the list of all subprojects of the modified project.
---

[victor]

Questions

am I right? or maybe is wrong my interpretation for the last zone in the notify filter case?

Anothe possible interpretation could be:

- Message parameters zone: The notification is only for tasks with one (or more) messages that make good all the defined filter conditions in this zone.

In message paramters zone you receive all messages. Your filter settings affect only subtasks zone, this is useful for filter subscription.

I think I didnt explain well my doubt about the message parameters zone:

When I define a filter condition in the message parameters zone is the subtask showed if any of its messages make good the message parameters zone condition or if the last message make good it?

The same question when I use the filter for e-mail notification.

One example showing like I suspect that actually this is running:
1 - I define a filter condition in the message parameters zone that say: 'submitter=peter'.
2 - If I apply the filter over subtasks list this condition mean that a subtask will be showed if it has some message where the submitter is peter.
3- If I use the filter to e-mail notification this condition mean that an e-mail notification will be generated if peter was the submitter of the last message.

Answer my questions, and if my suspects are right I think that this point could be documented (if I am wrong I have a problem with my filters ;)

Thanks

[admin]

I think I didnt explain well my doubt about the message parameters zone:

When I define a filter condition in the message parameters zone is the subtask showed if any of its messages make good the message parameters zone condition or if the last message make good it?

When it show messages - it apply conditions to all messages (show only messages with specified handler, for example).

The same question when I use the filter for e-mail notification.

When it decides should it send e-mail notification when user modify this task or not - it apply conditions to the last message only (send emil notification only when Administrator add new message, for example). But in such case we check only modified task, not their subtasks.

One example showing like I suspect that actually this is running:
1 - I define a filter condition in the message parameters zone that say: 'submitter=peter'.
2 - If I apply the filter over subtasks list this condition mean that a subtask will be showed if it has some message where the submitter is peter.
3- If I use the filter to e-mail notification this condition mean that an e-mail notification will be generated if peter was the submitter of the last message.

Yes, you right.

Answer my questions, and if my suspects are right I think that this point could be documented (if I am wrong I have a problem with my filters

Thanks

OK, we'll describe this feature more carefully in the documentation (as you can find, 2.8 docs have great progress over 2.7 docs in the most cumbersome areas).

[victor]

OK, we'll describe this feature more carefully in the documentation (as you can find, 2.8 docs have great progress over 2.7 docs in the most cumbersome areas).

Yes, you are doing a nice job.... Generally the human tend to detect the faults more better that the improvements and tend to accustom to the good things and tend to not value they when he has this good things. This is a principle of the 'human misery'.... Well, I am a very good example of the 'human misery' ;) ... my apologizes.

Jokes aside, of course I think that every day TS is a better system but I love be a free beta-critic, hahaha

Cheers Maxim, I am learning Java ;)

[admin]

OK, we'll describe this feature more carefully in the documentation (as you can find, 2.8 docs have great progress over 2.7 docs in the most cumbersome areas).

Yes, you are doing a nice job.... Generally the human tend to detect the faults more better that the improvements and tend to accustom to the good things and tend to not value they when he has this good things. This is a principle of the 'human misery'.... Well, I am a very good example of the 'human misery' ... my apologizes.

Jokes aside, of course I think that every day TS is a better system but I love be a free beta-critic, hahaha

Cheers Maxim, I am learning Java

Please check out LDAP patch (about backdoor), it should work fine - we just disallow empty passwords for LDAP authentication It seems that we should work with LDAP server in different way, we'll modify this in 3.0

[victor]

Only two things more...

- I define different filters to filter subtasks and notification filters.
- I want hide notification filters in the subtasks filters list.
- Some things have a different mean for subtasks filters and for notification filters.

This new detail does that I believe a bit more that subtask and notification filters are different things.

The other (an more important) thing: Yesterday you tell me about a filters sorting fix but I dont found where you tell me it. If I install the LDAP fix I need update another file to have the filter sorting fix too?

Thanks

[admin]

Only two things more...

- I define different filters to filter subtasks and notification filters.
- I want hide notification filters in the subtasks filters list.
- Some things have a different mean for subtasks filters and for notification filters.

This new detail does that I believe a bit more that subtask and notification filters are different things.

Yes. We'll implement different filters for e-mail notification & task filtering.

The other (an more important) thing: Yesterday you tell me about a filters sorting fix but I dont found where you tell me it. If I install the LDAP fix I need update another file to have the filter sorting fix too?

No, today I review developer's code and found that their fix cause another bug (items with equals names can disapper from UI). So this bug still in progress, possible we'll fix it tomorrow.

[victor]

No, today I review developer's code and found that their fix cause another bug (items with equals names can disapper from UI). So this bug still in progress, possible we'll fix it tomorrow.

Ok, I am going to test the solution to the ldap problem. Thanks

[victor]

- Test login root without password : Ok
- Test login root with bad password: Ok
- Test login root with right password: Ok

- Test login LDAP user without password: Ok
- Test login LDAP user with bad password: Ok
- Test login LDAP user with right password: Ok

Good job! Thanks!