It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787
×10,826
×514
×452

question asked: Apr 01 '16, 9:40 a.m.
question was seen: 2,328 times
last updated: Apr 04 '16, 12:21 a.m.

Related questions

FAQ - How this Forum works

Work item history tab shows an attribute that doesn't belongs to it when updating via OSLC API

0
Tiago Moura (838●7) | asked Apr 01 '16, 9:40 a.m.
edited Apr 01 '16, 12:25 p.m.
 Hello,

Here is my scenario:

I configured two types of work item X and Y. Then I configured a custom attribute (a1) on Y.

We have a service that update work items via OSLC API and we noticed that if I send an update to the work item X on the attribute a1 (that not belongs to X on the work item definition), the history tab shows that the attribute a1 was updated by my request.

How the history tab shows an attribute that not even belongs to the work item? Is it normal?


Att.

Tiago Moura

Accepted answer

0
permanent link
Donald Nong (14.5k●4●14) | answered Apr 04 '16, 12:21 a.m.
It's normal. Work item type is just one of the attributes of the work items. In fact, you can change the work item type either in the Web GUI or via API.
Tiago Moura 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.