#3 Fill external URL field
Merged by ralph. Opened by lsedlar.
lsedlar/sync-to-jira external-url  into  develop

Download 3.patch

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):

[f['id'] for f in jira.fields() if f['name'] == 'External issue URL']

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?

Whoah! I didn't see this.

Awesome! Will review asap.

Looks good. Will merge.

As for moving on with #1, we could make specifying an "external link" custom field a requirement. Having to manage code that handles two scenarios doesn't sound fun to me. :(

Pull-Request has been merged by ralph

Hm, we may also need some porting code here... such that older JIRA issues that don't have custom_10400 set can have it updated for them.

Metadata