The Jira integration only ingests issues modified since the last execution. Adding the custom field names later will mean that only when an issue is modified will we pick them up. It may be that we need a way to say, when the config is modified, tell the integration, and it can make a decision such as “re-fetch custom fields of all already-ingested issues”. This will have a performance impact in the case where there are many issues already in the system, so we'll need to consider that as part of designing a solution.
The Jira integration only ingests issues modified since the last execution. Adding the custom field names later will mean that only when an issue is modified will we pick them up. It may be that we need a way to say, when the config is modified, tell the integration, and it can make a decision such as “re-fetch custom fields of all already-ingested issues”. This will have a performance impact in the case where there are many issues already in the system, so we'll need to consider that as part of designing a solution.