It's all about the answers!

Ask a question

Synchronize Attributes as a server job on all open items?


Mike Shkolnik (9809161143) | asked Aug 01 '11, 6:27 p.m.
I see there are threads on this dating back to 2009 and was wondering if there are more recent developments.

When adding a new custom field, I often add it to Task, Story, Epic, and Defect. Therefore I need to "Synchronize Attributes" on all open work items. This is generally done manually by running an "all open items" query, selecting all items in the query with control-a, then right-clicking on the Type column and choosing "Synchronize Attributes". That worked fine in the beginning, but we have too many open work items now. I increased query results to 5000 work items, but selecting this many work items and running "Synchronize Attributes" results in "Error running operation 'Synchronizing Attributes'" after about 10 minutes. Thus I have to resort to using ID ranges to break the query into smaller pieces. This makes the process of manually synchronizing attributes quite the pain.

So I would really like to be able to tell the server to run the attribute sync at night. Is this possible yet, or is it still only a client-side manual process?

Accepted answer


permanent link
Geoffrey Clemm (30.1k33035) | answered Aug 01 '11, 8:27 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I've submitted work item 172944 for this enhancement.

Cheers,
Geoff

On 8/1/2011 6:38 PM, mshkolnik wrote:
When adding a new custom field, I often add it to Task, Story, Epic,
and Defect. Therefore I need to "Synchronize Attributes" on
all open work items. This is generally done manually by running an
"all open items" query, selecting all items in the query
with control-a, then right-clicking on the Type column and choosing
"Synchronize Attributes". That worked fine in the
beginning, but we have too many open work items now. I increased
query results to 5000 work items, but selecting this many work items
and running "Synchronize Attributes" results in "Error
running operation 'Synchronizing Attributes'" after about 10
minutes. Thus I have to resort to using ID ranges to break the query
into smaller pieces. This makes the process of manually synchronizing
attributes quite the pain.
Ralph Schoon selected this answer as the correct answer

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.