Filter subscription (newly created items for the last month)

Discuss problems installing or using TrackStudio.

Filter subscription (newly created items for the last month)

Postby waldorml » Mon Jul 06, 2009 3:51 pm

Hello,
A group that audits process compliance has requested a monthly notification containing all of the Tasks of a specific type and I've been tasked with providing it. I looked around the documentation and found a script for calculating the months since an item was created. I created a custom calculated field and bound it to the months since creation script. I then built a filter which looks for all items with 0 or 1 in the field and seem to get the right data. About 10 minutes after I finish this option, the response time for TS increases by 2 orders of magnitude (went from 20-40 msec to 5-10 minutes). When I was defining the custom field, I chose not to have the value cached (thinking it would make the database engine run off and calculate it for everything in the database). Would adding a non-cached calculated custom field to a database of about 7000 items cause that type of performance hit? Should it clear up? I have several users that must be able to use TS in a timely fashion.

If the method I chose to implement is causing the problem, is there an alternative that shouldn't have as much overhead? Ideally I'd like to be able to provide this information with minimal impact to normal data processing.
waldorml
 
Posts: 36
Joined: Thu Apr 16, 2009 3:02 pm

Re: Filter subscription (newly created items for the last mo

Postby admin » Thu Jul 09, 2009 1:08 am

Hello!

Sorry for delay. It seems like you don't require scripts there - just filter tasks by condition "submit date is 1 months before or later" - this will return tasks, which has been created last month. You can create filter subscription rule based on this filter to send this report every month at the same time.

You cannot use "cache" option there - it's possible to use it when script value depends on this task properties only (no other tasks properties, no system properties like current time). I think that 7000 tasks is a lot for any scripts (even caching) and if you decide to go this way - you need to reduce result set based on standard fields (filter out closed tasks, for example). TrackStudio evaluate calculated custom field value only when task pass all other conditions.
Maxim Kramarenko (mailto: maximkr@trackstudio.com)
TrackStudio - Hierarchical Bug & Issue Tracking Software
http://www.trackstudio.com
admin
Site Admin
 
Posts: 6528
Joined: Thu Jan 01, 1970 3:00 am
Location: Smolensk, Russia


Return to TrackStudio Support

Who is online

Users browsing this forum: No registered users and 1 guest