Downloaders/Parser/Refresher Function signatures

[carlosparadis]

@ian-lastname @Ssunoo2 @anthonyjlau

Could you paste here the list of function signatures your downloders/refreshers/parsers will have? I want to see side by side just to make sure we are not introducing inconsistencies (much as we noticed inconsistencies on the way data was stored by the issue trackers).

Just a bullet list of function signatures, no need to explain them here since they are already discussed in the respective issues.

[Ssunoo2]

Jira

• download_jira_issues()
• download_jira_issues_by_date()
• download_jira_issues_by_issue_key()
• refresh_jira_issues()

Github

• github_api_project_issue_refresh()

• github_api_project_issue_or_pr_comment_refresh

• These look different from the Jira ones that we agreed upon. I was attempting to follow the naming conventions for existing github functions. Here are some example of github download function names in github.R:

• github_api_project_issue_or_pr_comments

• github_api_project_pull_request

• github_api_project_issue

[ian-lastname]

Jira

• parse_jira(save_path)
• parse_jira_latest_date(save_path)

mbox

• mbox_download_refresh(current_latest_date, save_folder_path)
• mbox_parse_latest_date(save_folder_path)

[anthonyjlau]

Bugzilla

• download_bugzilla_rest_issues_comments(bugzilla_site, start_timestamp, save_folder_path, limit_upperbound = 500)
• parse_bugzilla_rest_issues(issues_folder_path)
• parse_bugzilla_rest_issues_comments(bugzilla_folder_path)