Geert van Horrik

4. Move $knownAssigneesMap (in export_jira_tickets.php) to .env

5. Re-use defined projects in jira_markdown.php

6. Improve knownIssueTypes in export_jira_tickets.php to this value: $knownIssueTypes = ['Bug', 'Epic', 'Question', 'Task', 'New Feature', 'Improvement'];

7. Fix ordering, issues are being created from 1 -> 10 -> 100 -> 1000, etc. While it would be better if they were being created from 1 => 1000

8. **Important**: wait with issue_numbers.php until they are all actually imported & created in GH (can take a while since export_jira_tickets only queues the tasks, GH does not create the...

9. Set the correct project inside generate_issues_map

I would vote yes

Thanks for reporting and the detailed error report. I will investigate this ASAP. Do you have a repo that I can use? E.g. do you have this code in a...

@Green7 I have written a unit test, but cannot reproduce. Can you double check the unit test is correct? * https://github.com/Catel/Catel.Fody/blob/develop/src/Catel.Fody.TestAssembly.Shared/Bugs/GH0511.cs * https://github.com/Catel/Catel.Fody/blob/develop/src/Catel.Fody.Tests.Shared/Repros/GH0511.cs

I added an extra check to check both the model and view model values: https://github.com/Catel/Catel.Fody/blob/feature/511-exposed-changed-notification/src/Catel.Fody.TestAssembly.Shared/Bugs/GH0511.cs#L41