You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The jira enriched index has a small discrepancy. There are two different items in jira index, issue and comment. The discrepancy is with two keys of the index, issue_type and issue_description.
item
issue_type
issue_description
issue
type of the issue (Bug, Story, Task, Epic, Sub-task)
description of the type of the issue
comment
description of the type of the issue
doesn't exist
Example:
{
"_index": "jira_onf_190624_enriched_220127",
...
"_source": {
"metadata__updated_on": "2022-05-09T21:45:36+00:00",
...
"issue_type": "Bug",
"issue_description": "A problem which impairs or prevents the functions of the product.",
...
"grimoire_creation_date": "2022-05-09T21:32:53+00:00",
"is_jira_issue": 1,
"type": "issue",
...
},
...
}
{
"_index": "jira_onf_190624_enriched_220127",
...
"_source": {
"metadata__updated_on": "2022-04-28T18:01:10+00:00",
...
"issue_key": "VOL-4710",
"issue_url": "https://jira.opencord.org/browse/VOL-4710",
"issue_type": "A problem which impairs or prevents the functions of the product.",
...
"type": "comment",
...
"grimoire_creation_date": "2022-04-28T18:01:10.930000+00:00",
"is_jira_comment": 1,
...
},
}
Is this the expected behavior? Does it make sense to have a common behavior between the two fields? I assume issue_type would have the type of the issue and issue_description would have the description of the type of the issue no matter if the item is a comment or issue.
Full issue item
{
"_index": "jira_onf_190624_enriched_220127",
"_type": "items",
"_id": "fd445f6f04d28747905649abd7a30cdfab0960e0_issue_89800_user_assignee",
"_version": 2,
"_score": null,
"_source": {
"metadata__updated_on": "2022-05-09T21:45:36+00:00",
"metadata__timestamp": "2022-05-09T21:51:02.454654+00:00",
"offset": null,
"origin": "https://jira.opencord.org",
"tag": "https://jira.opencord.org",
"uuid": "fd445f6f04d28747905649abd7a30cdfab0960e0",
"assignee": "Girish Gowdra",
"reporter": null,
"changes": 2,
"creator_name": "Girish Gowdru",
"creator_login": "ggowdra",
"creator_tz": "America/Los_Angeles",
"assignee_tz": "America/Los_Angeles",
"reporter_name": "Girish Gowdru",
"reporter_login": "ggowdra",
"reporter_tz": "America/Los_Angeles",
"author_type": "assignee",
"author_name": "Girish Gowdru",
"author_login": null,
"author_tz": "America/Los_Angeles",
"creation_date": "2022-05-09T21:32:53.000+0000",
"main_description": "ONU stuck in initial-mib-downloaded state after ONU reboot in periodic-voltha-unitag-subscriber-tt-test-bbsim tests.",
"main_description_analyzed": "ONU stuck in initial-mib-downloaded state after ONU reboot in periodic-voltha-unitag-subscriber-tt-test-bbsim tests.",
"issue_type": "Bug",
"issue_description": "A problem which impairs or prevents the functions of the product.",
"labels": [
"onf"
],
"priority": "Medium",
"progress_total": 0,
"project_id": "10106",
"project_key": "VOL",
"project_name": "VOLTHA",
"resolution_date": null,
"status_description": "This issue is being actively worked on at the moment by the assignee.",
"status": "In Progress",
"status_category_key": "indeterminate",
"is_closed": 0,
"summary": "ONU stuck in initial-mib-downloaded state after ONU reboot in periodic-voltha-unitag-subscriber-tt-test-bbsim tests",
"original_time_estimation": null,
"time_spent": null,
"time_estimation": null,
"watchers": 1,
"key": "VOL-4714",
"number_of_comments": 0,
"time_to_last_update_days": 0.05,
"url": "https://jira.opencord.org/browse/VOL-4714",
"id": "fd445f6f04d28747905649abd7a30cdfab0960e0_issue_89800_user_assignee",
"updated": "2022-05-09T21:45:36.000+0000",
"time_to_close_days": 0.01,
"releases": [
"VOLTHA v2.10"
],
"assignee_id": "82ca0ab60445dd153d91c29b651f843453f0702c",
"assignee_uuid": "2626840c9c1692c10f90dd242898ba663bccc687",
"assignee_name": "Girish Gowdru",
"assignee_user_name": "ggowdra",
"assignee_domain": "opennetworking.org",
"assignee_gender": "Unknown",
"assignee_gender_acc": 0,
"assignee_org_name": "Intel",
"assignee_bot": false,
"assignee_multi_org_names": [
"Intel"
],
"reporter_id": "82ca0ab60445dd153d91c29b651f843453f0702c",
"reporter_uuid": "2626840c9c1692c10f90dd242898ba663bccc687",
"reporter_user_name": "ggowdra",
"reporter_domain": "opennetworking.org",
"reporter_gender": "Unknown",
"reporter_gender_acc": 0,
"reporter_org_name": "Intel",
"reporter_bot": false,
"reporter_multi_org_names": [
"Intel"
],
"creator_id": "82ca0ab60445dd153d91c29b651f843453f0702c",
"creator_uuid": "2626840c9c1692c10f90dd242898ba663bccc687",
"creator_user_name": "ggowdra",
"creator_domain": "opennetworking.org",
"creator_gender": "Unknown",
"creator_gender_acc": 0,
"creator_org_name": "Intel",
"creator_bot": false,
"creator_multi_org_names": [
"Intel"
],
"author_id": "82ca0ab60445dd153d91c29b651f843453f0702c",
"author_uuid": "2626840c9c1692c10f90dd242898ba663bccc687",
"author_user_name": "ggowdra",
"author_domain": "opennetworking.org",
"author_gender": "Unknown",
"author_gender_acc": 0,
"author_org_name": "Intel",
"author_bot": false,
"author_multi_org_names": [
"Intel"
],
"project": "CORD",
"project_1": "CORD",
"grimoire_creation_date": "2022-05-09T21:32:53+00:00",
"is_jira_issue": 1,
"type": "issue",
"repository_labels": [],
"metadata__filter_raw": null,
"metadata__gelk_version": "0.100.0",
"metadata__gelk_backend_name": "JiraEnrich",
"metadata__enriched_on": "2022-05-09T22:51:46.034551+00:00"
},
"fields": {
"grimoire_creation_date": [
"2022-05-09T21:32:53.000Z"
],
"metadata__enriched_on": [
"2022-05-09T22:51:46.034Z"
],
"painless_delay": [
0.16666666666666666
],
"metadata__timestamp": [
"2022-05-09T21:51:02.454Z"
],
"creation_date": [
"2022-05-09T21:32:53.000Z"
],
"metadata__updated_on": [
"2022-05-09T21:45:36.000Z"
],
"updated": [
"2022-05-09T21:45:36.000Z"
],
"painless_time_to_now": [
0.16666666666666666
]
},
"sort": [
1652131973000
]
}
The text was updated successfully, but these errors were encountered:
vchrombie
changed the title
[jira] Discrepency with issue_type and issue_description
[jira] Discrepancy with issue_type and issue_descriptionMay 10, 2022
The jira enriched index has a small discrepancy. There are two different items in jira index,
issue
andcomment
. The discrepancy is with two keys of the index,issue_type
andissue_description
.issue_type
issue_description
issue
comment
Example:
Is this the expected behavior? Does it make sense to have a common behavior between the two fields? I assume
issue_type
would have the type of the issue andissue_description
would have the description of the type of the issue no matter if the item is acomment
orissue
.Full
issue
itemFull
comment
itemThe text was updated successfully, but these errors were encountered: