Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix bug where ClosedDate is unset for closed work items #812

Merged
merged 1 commit into from
Jul 24, 2023

Conversation

Alexander-Hjelm
Copy link
Collaborator

@Alexander-Hjelm Alexander-Hjelm commented Jul 24, 2023

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@Alexander-Hjelm Alexander-Hjelm merged commit 6f7610f into master Jul 24, 2023
@Alexander-Hjelm Alexander-Hjelm deleted the bugfix/field-closed-date-cannot-be-empty branch July 24, 2023 12:57
garooka pushed a commit to garooka/jira-azuredevops-migrator-extetion that referenced this pull request Sep 13, 2023
…e-cannot-be-empty

Fix bug where ClosedDate is unset for closed work items
garooka pushed a commit to garooka/jira-azuredevops-migrator-extetion that referenced this pull request Sep 13, 2023
…e-cannot-be-empty

Fix bug where ClosedDate is unset for closed work items
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When item that is closed is migrated, ADO shows: Field 'Closed Date' cannot be empty
1 participant