Hello,
I have used my own un-published solutions for Jira in R for years and I'm happy to finally see a clean public library for it.
One major hurdle are of course the custom fields. I am ready to help and wanted to throw a few potential solutions:
-
Adding an option to expose the entire raw JSON object to let the user pick the fields. From memory this is what the python module does.
-
Being able to locally define supported fields
-
Flattening the JSON object as much as possible to return everything in a data.frame. I seem to remember {jsonlite} or {httr} has solid options.
-
Using the /field API and store the result locally. This could allow JjirAgileR learn about the structure of the Jira instance.
I would need to test it further but it seems to describe which field is a date, an array etc. A different endpoint also returns the possible value of a field. This can be used to build the levels of a factor.
Hello,
I have used my own un-published solutions for Jira in R for years and I'm happy to finally see a clean public library for it.
One major hurdle are of course the custom fields. I am ready to help and wanted to throw a few potential solutions:
Adding an option to expose the entire raw JSON object to let the user pick the fields. From memory this is what the python module does.
Being able to locally define supported fields
Flattening the JSON object as much as possible to return everything in a data.frame. I seem to remember {jsonlite} or {httr} has solid options.
Using the
/fieldAPI and store the result locally. This could allow JjirAgileR learn about the structure of the Jira instance.I would need to test it further but it seems to describe which field is a date, an array etc. A different endpoint also returns the possible value of a field. This can be used to build the levels of a factor.