The emotional side of software developers in JIRA

Marco Ortu, Alessandro Murgia, Giuseppe Destefanis, Parastou Tourani, Roberto Tonelli, Michele Marchesi, Bram Adams

    Research output: Chapter in Book/Report/Conference proceedingConference contribution

    53 Citations (Scopus)


    Issue tracking systems store valuable data for testing hypotheses concerning maintenance, building statistical prediction models and (recently) investigating developer affectiveness. For the latter, issue tracking systems can be mined to explore developers emotions, sentiments and politeness |affects for short. However, research on affect detection in software artefacts is still in its early stage due to the lack of manually validated data and tools. In this paper, we contribute to the research of affects on software artefacts by providing a labeling of emotions present on issue comments. We manually labeled 2,000 issue comments and 4,000 sentences written by developers with emotions such as love, joy, surprise, anger, sadness and fear. Labeled comments and sentences are linked to software artefacts reported in our previously published dataset (containing more than 1K projects, more than 700K issue reports and more than 2 million issue comments). The enriched dataset presented in this paper allows the investigation of the role of affects in software development.
    Original languageEnglish
    Title of host publicationMSR '16: Proceedings of the 13th International Conference on Mining Software Repositories
    PublisherACM Press
    Number of pages4
    ISBN (Electronic)9781450341868
    Publication statusPublished - 14 May 2016
    Event13th Working Conference on Mining Software Repositories, MSR 2016 - Austin, United States
    Duration: 14 May 201615 May 2016


    Conference13th Working Conference on Mining Software Repositories, MSR 2016
    Country/TerritoryUnited States


    • Affective analysis
    • Issue reports
    • Mining software repositories


    Dive into the research topics of 'The emotional side of software developers in JIRA'. Together they form a unique fingerprint.

    Cite this