@vivekanand1101 @cverna do one of you want to look into this one?

This is odd because: https://pagure.io/pagure/blob/master/f/pagure/lib/git.py#_543

I will try to import once more to verify this.

@vivekanand1101 got any luck? (Should I assign the ticket to you?)

I tried twice but my import failed both the times thanks to my awesome internet connection. And currently, i don't have my project set up on my laptop. (formatted it). + I already have a LOT of things that i have told you i will do but, i haven't. Sorry, i won't be able to take this one currently.

One can try intra_pagure importer to check this issue btw.

@vivekanand1101 I ll give it a try tonight ;)

FWIW I discovered this when doing a test migration of mod_nss from fedorahosted to the pagure staging server.

The milestones are migrated to the issues but I had to manually add them as a milestone to be able to do queries based on it. Once I did that things worked nicely.

I agree, and we do need this. So coming from a trac import any custom field that matches a default field (like milestone, assignee, priority, etc) should populate that property in the Issue model, and not in the custom meta data. This also probably means that all the milestones coming from trac should/must be predefined in the pagure project prior to the import.

Perhaps this is really a pagure-importer issue?

@cverna @vivekanand1101 any luck with this one?

This issue went off my radar :) . Ill spend some time investigating .

@rcritten Could grant me XML_RPC rights on mod_nss so I can test the milestone import ?

Thanks

Fixed by @cverna in #1704