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

Custom field, old value migrated rather than null #801

Closed
RoyalWulf opened this issue Jul 7, 2023 · 6 comments
Closed

Custom field, old value migrated rather than null #801

RoyalWulf opened this issue Jul 7, 2023 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@RoyalWulf
Copy link

Describe the problem
A clear and concise description of what the problem/bug is.

Custom field in Jira called FixVersons had a value of "V45", this value was removed in Jira so now it has no value, but V45 was migrated as final value.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error
    run Jira-export and WI-Import

Tool version

  • Version of the jira-azuredevops-migrator tool [e.g. 2.3.117]
    3.0.136

Attachments

Please attach the following files:

  • config.json
  • jira-export-log.txt
  • wi-import-log.txt

Config.jso
config-agile_SMS2.json.txt

WI json file
US-26755 - Copy.json.txt

WI import log
wi-import-log-230707-115001.txt

Jira export file
jira-export-log-230707-114749.txt

Screenshots
If applicable, add screenshots to help explain your problem.

@Alexander-Hjelm
Copy link
Collaborator

I think we need more repro steps here.

How did you go about deleting the version? Did you delete the release itself, or did you clear the value of the fixesVersion field?

@Alexander-Hjelm Alexander-Hjelm added the bug Something isn't working label Jul 7, 2023
@RoyalWulf
Copy link
Author

Just cleared the value of the fix Versions field
Screenshot 2023-07-10 091122

@Alexander-Hjelm
Copy link
Collaborator

OK! Will look into it in the upcoming 2 weeks :)

@Alexander-Hjelm
Copy link
Collaborator

Fixed by #811. Reopen if the problem persists

@RoyalWulf
Copy link
Author

When will this fix be released?

@Alexander-Hjelm
Copy link
Collaborator

We released version 3.0.159 yesterday :)

@Alexander-Hjelm Alexander-Hjelm self-assigned this Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants