search

cronn / jira-sync

Jira-to-Jira synchronisation using the Jira REST API
Apache License 2.0
20 stars 13 forks source link

Info for ERROR 29381 #4

Closed teopost closed 6 years ago

teopost commented 6 years ago

Hi, I try to sync 2 jira projects with jira-sync but I have an error that I can not understand.

image

Is a very generic error! Can you help me understand what I'm wrong?

ldziedziul commented 6 years ago

Hi Stefano,

Could you provide a full stacktrace and re-run application with --debug?

teopost commented 6 years ago

Yes, This is the complete output log.txt

ldziedziul commented 6 years ago

Thanks!

Your log helped me a lot. You can see there a JiraResourceNotFoundException. The stacktrace indicates that there is a problem with the source filter settings:

de.cronn.jira.sync.projects[XXXX].sourceFilterId=<filterId>

Please double check that <filterId> points to the existing filter in your source Jira.

BTW. We need to improve our exceptions to be more descriptive ;)

teopost commented 6 years ago

My filterId is "allopenissues"

image

teopost commented 6 years ago

Hi @ldziedziul , I have created a custom filter. Now the error is different (I think): image

ldziedziul commented 6 years ago

I see. We've used custom filters so far which have always numeric id, allopenissues is a special case. A custom filter should resolve it.

Please send the log file with the full stacktrace again. This time without --debug

teopost commented 6 years ago

I think the problem is here: image but I don't have this field (I think) in the destination screen. sorry but I don't know how to setting parameters in application.properties. Can you explain the parameters of application.properties file ?

ldziedziul commented 6 years ago

I'm guessing without a stacktrace but currently we allways fetch the following fields using filters: summary,status,issuetype,description,priority,project,resolution,labels,versions,fixVersions,assignee,updated,comment

It looks like that for some reason you don't have versions and fixVersions fields which, we thought, are built-in (https://confluence.atlassian.com/adminjiraserver071/issue-fields-and-statuses-802592413.html).

Could you try to add a "1.0" version on both side to see if it helps?

You don't have to add the following lines to application.properties:

de.cronn.jira.sync.projects[XXX].versionMapping....

and 

de.cronn.jira.sync.projects[XXX].versionsToIgnore=Undefined

Version mapping is optional.

Background: These lines are used if you have different versions in both jira servers, e.g. 

de.cronn.jira.sync.projects[XXX].versionMapping[10.0]=10

means that you have version 10.0 in the source server and it has the same meaning as version 10 on the target server. If you don't configure versionMapping it will be omitted.

teopost commented 6 years ago

I have added Version 1.0 on both side but the result is the same.

log2.txt

application.properties.txt

Executed with this command line:

./build/libs/jira-sync-1.0.jar --spring.config.location=file:/Users/teopost/dev/jira-sync/config/application.properties

Some other info: The destination project is "Service Desk" type

ldziedziul commented 6 years ago

Hi. I've pushed the fix, please try now.

teopost commented 6 years ago

Thank you. Now work!