search

MicrosoftPremier / VstsExtensions

Documentation and issue tracking for Microsoft Premier Services Visual Studio Team Services Extensions
MIT License
57 stars 14 forks source link

"Assigned To" not optional #12

Closed papa-pep closed 6 years ago

papa-pep commented 6 years ago

It appears that the "Assigned To" field of the "Create Work Item" task is not optional as the documentation suggests. Can this be made optional?

Error in log: "Input required: assignedTo"

ReneSchumacher commented 6 years ago

Hey Greg,

sorry for that. I didn't realize I always tested with an identity and the code actually treated Assigned To as required. Give me about five minutes and I release an update.

Cheers, René

ReneSchumacher commented 6 years ago

The update is public. This should fix the issue. If not, please let me know an I'll reopen the issue.

papa-pep commented 6 years ago

Thank you!

papa-pep commented 6 years ago

I'm not sure it's related, but I can no longer view the build that contained the step. All others work fine.

image

It looks like a vsts update was just pushed too as the UI has changed.

ReneSchumacher commented 6 years ago

Hey, sorry for the late reply. I'm glad you confirmed that the issue is fixed now. The new issue shouldn't be related to the task update - at least I cannot think of any way a new task version should impact the rendering of the build summary UI.

If I understand your addition correctly, the second issue is gone by now? Otherwise I might be able to help investigate the root cause.

papa-pep commented 6 years ago

I'm still experiencing the error mentioned above. I've also opened a ticket with vsts but haven't received a reply yet.

papa-pep commented 6 years ago

Case number: 118083018897642