{"id":{"repo_id":"lethbridge","oai_identifier":"oai:opus.uleth.ca:10133/6415"},"canonical_url":"https://search.dev.ndltd.org/etd/lethbridge/oai:opus.uleth.ca:10133/6415","repository":{"repo_id":"lethbridge","name":"University of Lethbridge","base_url":"https://opus.uleth.ca/server/oai/request"},"display":{"title":"Detecting planning conversations in bug reports","abstract":"Software developers refer to bug reports as a reliable source of information. However, these bug reports are written in the form of conversations among developers and often become long depending on the complexity of the issue, necessitating a significant amount of time and effort to locate the desired information. Prior work focused on tagging the different types of information in the bug reports. However, their work did not identify Plans. In our work, we focus on retrieving Plans from bug reports and labeling them with a Plan Labeller. First, we analyzed bug reports to identify which section contains Plans. Then we examined three methods to detect Plans. Based on that, we found keywords and key-phrases to be the best approach. We applied lists of keywords and key-phrases iteratively to randomly selected bug reports to construct a list of keywords and key-phrases that can identify Plans in a bug report.","abstract_html":"Software developers refer to bug reports as a reliable source of information. However, these bug reports are written in the form of conversations among developers and often become long depending on the complexity of the issue, necessitating a significant amount of time and effort to locate the desired information. Prior work focused on tagging the different types of information in the bug reports. However, their work did not identify Plans. In our work, we focus on retrieving Plans from bug reports and labeling them with a Plan Labeller. First, we analyzed bug reports to identify which section contains Plans. Then we examined three methods to detect Plans. Based on that, we found keywords and key-phrases to be the best approach. We applied lists of keywords and key-phrases iteratively to randomly selected bug reports to construct a list of keywords and key-phrases that can identify Plans in a bug report.","abstract_has_math":false,"creators":["Islam, Rafat Bin","University of Lethbridge. Faculty of Arts and Science"],"institution":"Lethbridge, Alta. : University of Lethbridge, Dept. of Mathematics and Computer Science","degree_name":null,"degree_level":null,"degree_discipline":null,"degree_department":null,"school":null,"contributors":[],"advisors":["Anvik, John"],"committee_chairs":[],"committee_members":[],"year":2022,"date_issued":"2022-12-14","date_published":"2022-12-14","updated_at":"2026-08-21T16:45:58Z","subjects":["Bug reports","Plan labeller","List of keywords and key-phrases","Manually labeled sentences","Automatic sentence annotation","Tagging","Annotated dataset","Software bugs"],"languages":["en"],"rights":[],"rights_urls":[],"identifier_entries":[{"key":"dc:identifier","label":"Identifier","values":["hdl:10133/6415"],"render_values":[{"text":"hdl:10133/6415","href":null,"code":true}]}]},"links":{"outbound_url":"https://hdl.handle.net/10133/6415","outbound_label":"Handle","outbound_source":"dc:identifier.uri"},"source_record":{"url":"https://opus.uleth.ca/server/oai/request?verb=GetRecord&metadataPrefix=dim&identifier=oai%3Aopus.uleth.ca%3A10133%2F6415","prefix":"dim"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor.supervisor","label":"Supervisor","values":["Anvik, John"]},{"key":"dc:creator","label":"Author","values":["Islam, Rafat Bin","University of Lethbridge. Faculty of Arts and Science"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date.accessioned","label":"Dc Date Accessioned","values":["2023-01-23T18:13:55Z"]},{"key":"dc:date.available","label":"Dc Date Available","values":["2023-01-23T18:13:55Z"]},{"key":"dc:date.issued","label":"Date","values":["2022-12-14"]},{"key":"dc:publisher","label":"Institution","values":["Lethbridge, Alta. : University of Lethbridge, Dept. of Mathematics and Computer Science"]},{"key":"dc:publisher.department","label":"Dc Publisher Department","values":["Department of Mathematics and Computer Science"]},{"key":"dc:type","label":"Dc Type","values":["Thesis"]}]},{"id":"subjects_keywords","label":"Subjects and Keywords","entries":[{"key":"dc:subject","label":"Dc Subject","values":["Bug reports","Plan labeller","List of keywords and key-phrases","Manually labeled sentences","Automatic sentence annotation","Tagging","Annotated dataset","Software bugs"]}]},{"id":"language_rights","label":"Language and Rights","entries":[{"key":"dc:language.iso","label":"Language (ISO)","values":["en"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier","label":"Identifier","values":["hdl:10133/6415"]},{"key":"dc:identifier.uri","label":"Identifier URI","values":["https://hdl.handle.net/10133/6415"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description.abstract","label":"Abstract","values":["Software developers refer to bug reports as a reliable source of information. However, these bug reports are written in the form of conversations among developers and often become long depending on the complexity of the issue, necessitating a significant amount of time and effort to locate the desired information. Prior work focused on tagging the different types of information in the bug reports. However, their work did not identify Plans. In our work, we focus on retrieving Plans from bug reports and labeling them with a Plan Labeller. First, we analyzed bug reports to identify which section contains Plans. Then we examined three methods to detect Plans. Based on that, we found keywords and key-phrases to be the best approach. We applied lists of keywords and key-phrases iteratively to randomly selected bug reports to construct a list of keywords and key-phrases that can identify Plans in a bug report."]},{"key":"dc:description.other","label":"Dc Description Other","values":["Software developers refer to bug reports as a reliable source of information. However, these bug reports are written in the form of conversations among developers and often become long depending on the complexity of the issue, necessitating a significant amount of time and effort to locate the desired information. Prior work focused on tagging the different types of information in the bug reports. However, their work did not identify Plans. In our work, we focus on retrieving Plans from bug reports and labeling them with a Plan Labeller. First, we analyzed bug reports to identify which section contains Plans. Then we examined three methods to detect Plans. Based on that, we found keywords and key-phrases to be the best approach. We applied lists of keywords and key-phrases iteratively to randomly selected bug reports to construct a list of keywords and key-phrases that can identify Plans in a bug report."]},{"key":"dc:title","label":"Title","values":["Detecting planning conversations in bug reports"]}]}],"canonical_facts":{"dc:contributor.supervisor":["Anvik, John"],"dc:creator":["Islam, Rafat Bin","University of Lethbridge. Faculty of Arts and Science"],"dc:date.accessioned":["2023-01-23T18:13:55Z"],"dc:date.available":["2023-01-23T18:13:55Z"],"dc:date.issued":["2022-12-14"],"dc:description.abstract":["Software developers refer to bug reports as a reliable source of information. However, these bug reports are written in the form of conversations among developers and often become long depending on the complexity of the issue, necessitating a significant amount of time and effort to locate the desired information. Prior work focused on tagging the different types of information in the bug reports. However, their work did not identify Plans. In our work, we focus on retrieving Plans from bug reports and labeling them with a Plan Labeller. First, we analyzed bug reports to identify which section contains Plans. Then we examined three methods to detect Plans. Based on that, we found keywords and key-phrases to be the best approach. We applied lists of keywords and key-phrases iteratively to randomly selected bug reports to construct a list of keywords and key-phrases that can identify Plans in a bug report."],"dc:description.other":["Software developers refer to bug reports as a reliable source of information. However, these bug reports are written in the form of conversations among developers and often become long depending on the complexity of the issue, necessitating a significant amount of time and effort to locate the desired information. Prior work focused on tagging the different types of information in the bug reports. However, their work did not identify Plans. In our work, we focus on retrieving Plans from bug reports and labeling them with a Plan Labeller. First, we analyzed bug reports to identify which section contains Plans. Then we examined three methods to detect Plans. Based on that, we found keywords and key-phrases to be the best approach. We applied lists of keywords and key-phrases iteratively to randomly selected bug reports to construct a list of keywords and key-phrases that can identify Plans in a bug report."],"dc:identifier":["hdl:10133/6415"],"dc:identifier.uri":["https://hdl.handle.net/10133/6415"],"dc:language.iso":["en"],"dc:publisher":["Lethbridge, Alta. : University of Lethbridge, Dept. of Mathematics and Computer Science"],"dc:publisher.department":["Department of Mathematics and Computer Science"],"dc:subject":["Bug reports","Plan labeller","List of keywords and key-phrases","Manually labeled sentences","Automatic sentence annotation","Tagging","Annotated dataset","Software bugs"],"dc:title":["Detecting planning conversations in bug reports"],"dc:type":["Thesis"]},"updated_at":"2026-08-21T16:45:58Z"}