Dealing with custom fields

[MadEarl]

I've made some additions to enable dealing with custom fields, and I wanted initially to have this completely configurable so that one can add some config keys and have their additions working. However, this turned out to be a huge hassle with converting between names, keywords, and customfield values.

I'm wondering if it would make sense to put this logic in a mapping list that contains org-property key, keyword, Jira field name, and alist traversal information, and that is queried by each modifier function. That way, it would be fairly easy to customize and add new fields.

[nyyManni]

Sounds like a good idea to have an alist for custom fields that would be mapped into properties.

The custom fields for epic and sprint would still remain as separate variables, as they have a semantic meaning in ejira.