We the students of IIIT Hyderabad (https://iiit.ac.in), as part of our research on improving the features provided by Bug Tracking tools, we are reaching out to Open Source Software (OSS) Development Community to capture your feedback on your experiences on using bug tracking tools as part of your OSS product development. Please go through below questions and share your feedback. We really appreciate if you can share the survey to your fellow teammates and help us reaching out to maximum software practitioners in OSS community. If you have any queries please feel free to drop us an email at [sai.anirudh@research.iiit.ac.in] or [anveshi.shukla@research.iiit.ac.in]

If you have trouble viewing or submitting this form, you can fill it in in Google Forms.

Survey on Bug Tracking Tools

We the students of IIIT Hyderabad (https://iiit.ac.in), as part of our research on improving the features provided by Bug Tracking tools, we are reaching out to Open Source Software (OSS) Development Community to capture your feedback on your experiences on using bug tracking tools as part of your OSS product development. Please go through below questions and share your feedback. We really appreciate if you can share the survey to your fellow teammates and help us reaching out to maximum software practitioners in OSS  community. If you have any queries please feel free to drop us an email at [sai.anirudh@research.iiit.ac.in] or [anveshi.shukla@research.iiit.ac.in]
*Required

Name of your Open Source Project *

How many years of work experience you have in area of Software Maintenance (As a Bug reporter/Bug fixer/ QA Manager or developer )? *

Less than 1 years
Between 1 and 5 years
More than 5 years
Other:

Which Bug tracking tool is used for your Open Source Project ?

As a Software maintenance professional (bug reporter, bug fixer, QA Engineer or developer) How important the bug tracking tool is for your Open source project ? *

High (We cannot work with out it)
Moderate (We just need it)
Partially (Not so important)
Low (We don't use any)

As a Software maintenance professional (bug reporter, bug fixer, QA Engineer or developer) Does your bug tracking tool meet all your requirements ? *

Yes - 100% (it covers all our requirements)
Moderate - 75% - 100% (it covers almost all requirements)
Partially - 50% - 75% (it partially covers our requirements)
No - below 50% (it don't, but we got habituated to it)

As a bug reporter, Does your bug tracking tool help you share all required details without any changes made to existing tool (with no additional API) ? *

Yes - 100% (all options are readily available)
Moderate - 75% - 100% (We use APIs for few options)
Partially - 50% - 75% (We use APIs for almost all options)
No - below 50% (We completely depend on external API)

As a Bug fixer, Does your bug report explain everything you need to fix the issue ? Yes - 100% (Bug report has all required features) *

Yes - 100% (Bug report has all required features)
Moderate - 75% - 100% (We customized few options on our bug report)
Partially - 50% - 75% (We customized almost all options on our bug report)
No - below 50% (We use completely a custom bug report)

Does your bug tracking tool provide all desired/standard features (Customizable Bug template/Reporting/Trend Analysis/Archive etc.) ? *

Yes - 100% (meets all desired features)
Moderate - 75% - 100% (meets all almost all features)
Partially - 50% - 75% (meets only few features, we depend on APIs for desired features)
No - below 50%(Very few features, we completely depend on APIs for desired features)

What are the features which are desirable but not provided by your bug tracking tool ? *