It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,878
×4,715
×53
×17

question asked: Nov 11 '15, 3:25 a.m.
question was seen: 2,659 times
last updated: Nov 11 '15, 5:12 a.m.

Related questions

Should "synchronize" always count as a work item change?

0
Erik Mats (105●1●11●25) | asked Nov 11 '15, 3:25 a.m.
edited Nov 11 '15, 4:06 a.m.

Say you have modified your process configuration to add a new value to an enumeration. You "synchronize" all your project's work items to allow users to employ the new value.

This "synchronize" operation has at least three consequences which I wonder whether they are intended:
* This is recorded as an empty change in the work item history
* An e-mail notification is sent out to each subscriber
* The work item will be picked up by Java ETL builds such as WorkItemHistory and WorkItemBaseline.

Is this intended behavior or maybe a defect?

Observed in RTC 4.0.3.

Accepted answer

0
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Nov 11 '15, 5:12 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Nov 11 '15, 5:12 a.m.
You only need to "synchronize" if you added new attributes to a work item type and want to introduce them to all existing work items of that type.
In general "synchronize" attributes reapplies the type. What you see is by design, if you disagree, please create an enhancement request.
Erik Mats 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.