> I need more structured and reliable access to issue metadata... Please be specific about the structure(s) and reliability you need. Are you able to access the necessary data currently but it's unstructured and/or unreliable?
> Consistent and complete export of issue fields (e.g., creation and > resolution dates, linked commits, issue types, and resolutions) Why can't you get this information now? There is publicly available export functionality available in every Jira project (e.g. here [1] for ActiveMQ Artemis). Do you need specific fields that are not available via this export? > Filtering and searching across a large number of historical issues... You can filter and search across essentially every issue ever created using the Jira Query Language [2]. > Accessing API endpoints that may require authentication to handle higher > request limits or structured queries. As noted above, structure queries are already available. However, higher request limits almost certainly cannot be granted as the ASF Infrastructure team has to account for the needs of thousands of users across over 150 different Jira projects. I specifically discussed your account request with the ASF Infrastructure team and they denied it based on the fact that all the information you need should already be publicly available and so far you have not provided any specific evidence to the contrary. > This level of access is necessary to ensure data completeness and minimize > noise when linking issues to commits... The data which is publicly available should be sufficiently complete. If it isn't please provide specific examples. It's not clear what you mean by "noise" in this context. Keep in mind that the ASF Jira is designed to be used and searched by non-registered users. You only need an account to create, comment or vote on, or watch issues. Lastly, it's worth noting that we've had 3 other similar requests for accounts to do research this calendar year, and they've all been denied. Justin [1] https://issues.apache.org/jira/browse/ARTEMIS-5569?jql=project%20%3D%20ARTEMIS (see the "Export" button on the top right) [2] https://www.atlassian.com/software/jira/guides/jql/cheat-sheet#intro-to-jql On Sat, Oct 11, 2025 at 11:45 AM Haninda Faisa Nurrofifah <[email protected]> wrote: > Dear ActiveMQ Community, > > My name is Haninda Faisa Nurrofifah, an undergraduate student of Computer > Engineering at Universitas Muhammadiyah Surakarta, Indonesia. I am > currently conducting academic research on software repository mining, > focusing on identifying bug-introducing changes in Apache projects using > the SZZ algorithm. > > Previously, I submitted a Jira account request for the ActiveMQ project, > but it was denied because the requested information is considered publicly > available. I fully respect this policy, and I understand that most issue > data can indeed be viewed without logging in. > > However, for my research, I need more structured and reliable access to > issue metadata, including: > - Consistent and complete export of issue fields (e.g., creation and > resolution dates, linked commits, issue types, and resolutions), > - Filtering and searching across a large number of historical issues, > - Accessing API endpoints that may require authentication to handle higher > request limits or structured queries. > > This level of access is necessary to ensure data completeness and minimize > noise when linking issues to commits, which is a critical step in > implementing the SZZ algorithm accurately. I believe this will > significantly improve the quality and reproducibility of my research > results. > > If possible, I would be very grateful for any of the following: > - Guidance on how to formally request limited Jira account access for > academic research purposes, > - Recommendation of alternative official methods to export or access > complete issue metadata for ActiveMQ, > - Or, if the community deems it appropriate, sponsorship or endorsement for > a Jira account to support this research. > > I truly appreciate your time and consideration. I highly value the > open-source community’s contribution, and this research aims to deepen > understanding of bug-fix patterns and software quality evolution in Apache > projects. > > Warm regards, > Haninda Faisa Nurrofifah > Undergraduate Student – Computer Engineering > Universitas Muhammadiyah Surakarta, Indonesia > > -- > > > > > Email ini dikirimkan oleh Universitas Muhammadiyah Surakarta (UMS). > Jika Anda tidak ingin lagi menerima email serupa, silakan klik tautan > berhenti berlangganan (unsubscribe). Apabila tautan tersebut tidak > tersedia, atau jika Anda menganggap email ini sebagai sebuah kesalahan > atau > spam, mohon laporkan kepada Tim IT kami melalui [LINK > <https://forms.gle/XUzFgWzAsSw6dVcY9>] untuk mendapatkan bantuan. > > > **This > email was sent by Universitas Muhammadiyah Surakarta (UMS). If you no > longer wish to receive similar emails, please click the unsubscribe link. > If the link is not available, or if you believe this email is a mistake or > spam, please report it to our IT Team via [LINK > <https://forms.gle/XUzFgWzAsSw6dVcY9>] for assistance.* > * > >
