Jira can have custom fields. There might be a field called "External Issue URL", which should probably be filled in during the sync. The name really isn't that important, as the api uses a customfield_XXXXX for it and the nice name is only for displaying to users.
With this patch, the config can specify name of the field, and that field will be used. Name of the field can be found with this snippet (assuming jira is an instance of jira.client.JIRA):
This solves part of #1. I'm not sure how to move on from this. If the sync is supposed to work with arbitrary Jira instance, should there be fallback for those without any suitable field? Should the sync require such custom field?
Jira can have custom fields. There might be a field called "External Issue URL", which should probably be filled in during the sync. The name really isn't that important, as the api uses a
customfield_XXXXXfor it and the nice name is only for displaying to users.With this patch, the config can specify name of the field, and that field will be used. Name of the field can be found with this snippet (assuming
jirais an instance ofjira.client.JIRA):This solves part of #1. I'm not sure how to move on from this. If the sync is supposed to work with arbitrary Jira instance, should there be fallback for those without any suitable field? Should the sync require such custom field?