Cannot update WorkItems - Reason: TF237124: Work Item is not ready to save“TF237124: Work Item is not ready to save” on associated workitem, but code is checked in regardlessCannot import the keyfile 'blah.pfx' - error 'The keyfile may be password protected'Visual Studio debugging/loading very slowdifference between Product Backlog Item and Feature in Team Foundation work item typesVisual Studio Team Services Import HistoryMultiple Errors Installing Visual Studio 2015 Community EditionHow to migrate work items from TFS to Visual Studio Team ServicesCannot resolve work items in Team Foundation ServicesVisual Studio 2017 - Git failed with a fatal errorVisual Studio 2017 - Open Folder - TFVC IntegrationGet TFS associated work item of a checkin (not changeset)
Integer addition + constant, is it a group?
Proof of work - lottery approach
How long to clear the 'suck zone' of a turbofan after start is initiated?
Tiptoe or tiphoof? Adjusting words to better fit fantasy races
Short story about space worker geeks who zone out by 'listening' to radiation from stars
Is expanding the research of a group into machine learning as a PhD student risky?
Do the temporary hit points from the Battlerager barbarian's Reckless Abandon stack if I make multiple attacks on my turn?
Is the destination of a commercial flight important for the pilot?
CREATE opcode: what does it really do?
How does buying out courses with grant money work?
Is there a good way to store credentials outside of a password manager?
How do I find the solutions of the following equation?
Sort a list by elements of another list
Is `x >> pure y` equivalent to `liftM (const y) x`
Would a high gravity rocky planet be guaranteed to have an atmosphere?
Hostile work environment after whistle-blowing on coworker and our boss. What do I do?
Roman Numeral Treatment of Suspensions
Is a stroke of luck acceptable after a series of unfavorable events?
Large drywall patch supports
Pre-amplifier input protection
Class Action - which options I have?
What is the difference between "behavior" and "behaviour"?
Fine Tuning of the Universe
What is the best translation for "slot" in the context of multiplayer video games?
Cannot update WorkItems - Reason: TF237124: Work Item is not ready to save
“TF237124: Work Item is not ready to save” on associated workitem, but code is checked in regardlessCannot import the keyfile 'blah.pfx' - error 'The keyfile may be password protected'Visual Studio debugging/loading very slowdifference between Product Backlog Item and Feature in Team Foundation work item typesVisual Studio Team Services Import HistoryMultiple Errors Installing Visual Studio 2015 Community EditionHow to migrate work items from TFS to Visual Studio Team ServicesCannot resolve work items in Team Foundation ServicesVisual Studio 2017 - Git failed with a fatal errorVisual Studio 2017 - Open Folder - TFVC IntegrationGet TFS associated work item of a checkin (not changeset)
I am using Visual Studio 2017 (15.9.8) with an on-premise installation of TFS 2017.
In our team a checkin is required to have some associated work item. This worked fine and does still with all of my colleagues.
But when I do a checkin, I get the error message (see title) with every work item I associate. Since checkin works fine, it is just annoying to associate the change sets manually.
I do not use any custom code, so I can't debug any API (as suggested by Shayki Abramczyk) - it's just a matter between VS and TFS. I tried to intercept the communication between VS and TFS, but that did not work yet.
How can I find out which fields are invalid? Is there any type of log where I can research the cause?
Guenter
visual-studio tfs visual-studio-2017
asked Mar 7 at 12:57
GuenterGuenter
313
|
show 2 more comments
I am using Visual Studio 2017 (15.9.8) with an on-premise installation of TFS 2017.
In our team a checkin is required to have some associated work item. This worked fine and does still with all of my colleagues.
But when I do a checkin, I get the error message (see title) with every work item I associate. Since checkin works fine, it is just annoying to associate the change sets manually.
I do not use any custom code, so I can't debug any API (as suggested by Shayki Abramczyk) - it's just a matter between VS and TFS. I tried to intercept the communication between VS and TFS, but that did not work yet.
How can I find out which fields are invalid? Is there any type of log where I can research the cause?
Guenter
visual-studio tfs visual-studio-2017
asked Mar 7 at 12:57
GuenterGuenter
313
Possible duplicate of "TF237124: Work Item is not ready to save" on associated workitem, but code is checked in regardless
– Shayki Abramczyk
Mar 7 at 14:29
This is not a duplicate because the problem of dan is inside his own code using the TFS API. My problem is in the product itself, so I cannot use the suggested solution for the other question (calling the Validate() method of TFS API) as I don't know which fields are changed by the TFS checkin procedure.
– Guenter
Mar 8 at 11:59
You can try update the work item via API and use the Validate(), then you will see which field is the problem.
– Shayki Abramczyk
Mar 8 at 12:36
Shayki, please read my post before answering; as I do not own the code that modifies the work items, I cannot use any API to verify, because I don't know which field to change to produce the error! I need a means to log/intercept the communication between VS2017 anf the TFS server to identify the changed fields ikn the first place...
– Guenter
Mar 10 at 19:03
You don't need to be the own of the code, you can write your code and retrieve the work item with the API, then check the fields.
– Shayki Abramczyk
Mar 10 at 19:04
|
show 2 more comments
I am using Visual Studio 2017 (15.9.8) with an on-premise installation of TFS 2017.
In our team a checkin is required to have some associated work item. This worked fine and does still with all of my colleagues.
But when I do a checkin, I get the error message (see title) with every work item I associate. Since checkin works fine, it is just annoying to associate the change sets manually.
I do not use any custom code, so I can't debug any API (as suggested by Shayki Abramczyk) - it's just a matter between VS and TFS. I tried to intercept the communication between VS and TFS, but that did not work yet.
How can I find out which fields are invalid? Is there any type of log where I can research the cause?
Guenter
visual-studio tfs visual-studio-2017
asked Mar 7 at 12:57
GuenterGuenter
313
I am using Visual Studio 2017 (15.9.8) with an on-premise installation of TFS 2017.
In our team a checkin is required to have some associated work item. This worked fine and does still with all of my colleagues.
But when I do a checkin, I get the error message (see title) with every work item I associate. Since checkin works fine, it is just annoying to associate the change sets manually.
I do not use any custom code, so I can't debug any API (as suggested by Shayki Abramczyk) - it's just a matter between VS and TFS. I tried to intercept the communication between VS and TFS, but that did not work yet.
How can I find out which fields are invalid? Is there any type of log where I can research the cause?
Guenter
visual-studio tfs visual-studio-2017
visual-studio tfs visual-studio-2017
asked Mar 7 at 12:57
GuenterGuenter
313
asked Mar 7 at 12:57
GuenterGuenter
313
edited Mar 8 at 12:12
Guenter
asked Mar 7 at 12:57
GuenterGuenter
313
asked Mar 7 at 12:57
GuenterGuenter
313
asked Mar 7 at 12:57
GuenterGuenter
313
313
Possible duplicate of "TF237124: Work Item is not ready to save" on associated workitem, but code is checked in regardless
– Shayki Abramczyk
Mar 7 at 14:29
This is not a duplicate because the problem of dan is inside his own code using the TFS API. My problem is in the product itself, so I cannot use the suggested solution for the other question (calling the Validate() method of TFS API) as I don't know which fields are changed by the TFS checkin procedure.
– Guenter
Mar 8 at 11:59
You can try update the work item via API and use the Validate(), then you will see which field is the problem.
– Shayki Abramczyk
Mar 8 at 12:36
Shayki, please read my post before answering; as I do not own the code that modifies the work items, I cannot use any API to verify, because I don't know which field to change to produce the error! I need a means to log/intercept the communication between VS2017 anf the TFS server to identify the changed fields ikn the first place...
– Guenter
Mar 10 at 19:03
You don't need to be the own of the code, you can write your code and retrieve the work item with the API, then check the fields.
– Shayki Abramczyk
Mar 10 at 19:04
|
show 2 more comments
Possible duplicate of "TF237124: Work Item is not ready to save" on associated workitem, but code is checked in regardless
– Shayki Abramczyk
Mar 7 at 14:29
This is not a duplicate because the problem of dan is inside his own code using the TFS API. My problem is in the product itself, so I cannot use the suggested solution for the other question (calling the Validate() method of TFS API) as I don't know which fields are changed by the TFS checkin procedure.
– Guenter
Mar 8 at 11:59
You can try update the work item via API and use the Validate(), then you will see which field is the problem.
– Shayki Abramczyk
Mar 8 at 12:36
Shayki, please read my post before answering; as I do not own the code that modifies the work items, I cannot use any API to verify, because I don't know which field to change to produce the error! I need a means to log/intercept the communication between VS2017 anf the TFS server to identify the changed fields ikn the first place...
– Guenter
Mar 10 at 19:03
You don't need to be the own of the code, you can write your code and retrieve the work item with the API, then check the fields.
– Shayki Abramczyk
Mar 10 at 19:04
Possible duplicate of "TF237124: Work Item is not ready to save" on associated workitem, but code is checked in regardless
– Shayki Abramczyk
Mar 7 at 14:29
Possible duplicate of "TF237124: Work Item is not ready to save" on associated workitem, but code is checked in regardless
– Shayki Abramczyk
Mar 7 at 14:29
This is not a duplicate because the problem of dan is inside his own code using the TFS API. My problem is in the product itself, so I cannot use the suggested solution for the other question (calling the Validate() method of TFS API) as I don't know which fields are changed by the TFS checkin procedure.
– Guenter
Mar 8 at 11:59
This is not a duplicate because the problem of dan is inside his own code using the TFS API. My problem is in the product itself, so I cannot use the suggested solution for the other question (calling the Validate() method of TFS API) as I don't know which fields are changed by the TFS checkin procedure.
– Guenter
Mar 8 at 11:59
You can try update the work item via API and use the Validate(), then you will see which field is the problem.
– Shayki Abramczyk
Mar 8 at 12:36
You can try update the work item via API and use the Validate(), then you will see which field is the problem.
– Shayki Abramczyk
Mar 8 at 12:36
Shayki, please read my post before answering; as I do not own the code that modifies the work items, I cannot use any API to verify, because I don't know which field to change to produce the error! I need a means to log/intercept the communication between VS2017 anf the TFS server to identify the changed fields ikn the first place...
– Guenter
Mar 10 at 19:03
Shayki, please read my post before answering; as I do not own the code that modifies the work items, I cannot use any API to verify, because I don't know which field to change to produce the error! I need a means to log/intercept the communication between VS2017 anf the TFS server to identify the changed fields ikn the first place...
– Guenter
Mar 10 at 19:03
You don't need to be the own of the code, you can write your code and retrieve the work item with the API, then check the fields.
– Shayki Abramczyk
Mar 10 at 19:04
You don't need to be the own of the code, you can write your code and retrieve the work item with the API, then check the fields.
– Shayki Abramczyk
Mar 10 at 19:04
|
show 2 more comments
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55044373%2fcannot-update-workitems-reason-tf237124-work-item-is-not-ready-to-save%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55044373%2fcannot-update-workitems-reason-tf237124-work-item-is-not-ready-to-save%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Possible duplicate of "TF237124: Work Item is not ready to save" on associated workitem, but code is checked in regardless
– Shayki Abramczyk
Mar 7 at 14:29
This is not a duplicate because the problem of dan is inside his own code using the TFS API. My problem is in the product itself, so I cannot use the suggested solution for the other question (calling the Validate() method of TFS API) as I don't know which fields are changed by the TFS checkin procedure.
– Guenter
Mar 8 at 11:59
You can try update the work item via API and use the Validate(), then you will see which field is the problem.
– Shayki Abramczyk
Mar 8 at 12:36
Shayki, please read my post before answering; as I do not own the code that modifies the work items, I cannot use any API to verify, because I don't know which field to change to produce the error! I need a means to log/intercept the communication between VS2017 anf the TFS server to identify the changed fields ikn the first place...
– Guenter
Mar 10 at 19:03
You don't need to be the own of the code, you can write your code and retrieve the work item with the API, then check the fields.
– Shayki Abramczyk
Mar 10 at 19:04