Support other bug tracker when parse problem list and query corresponding bug tracker status
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
For now we also exclude test by [openjdk bug tracker](https://bugs.openjdk.java.net/projects/JDK/issues/JDK-8274381?filter=allopenissues) in Adoptium/aqa-tests. Probably azure devops also has its bug trackers or other vendors may have their own bug trackers.
To support that we can
1. Enhance #2858 by updating GIT_ISSUE to ISSUE_TRACKER, https://github.com/adoptium/aqa-tests/issues/2906
2. Enhance #2882 by updating GIT_ISSUE_STATUS to ISSUE_TRACKER_STATUS. To do that query different bug tracker status would be needed. For now we can first start with query [openjdk bug tracker](https://bugs.openjdk.java.net/projects/JDK/issues/JDK-8274381?filter=allopenissues), https://github.com/adoptium/aqa-tests/issues/2907
Related with https://github.com/adoptium/aqa-tests/issues/2698
https://github.com/adoptium/aqa-tests/issues/1853
Contributor guide
Research direction
Start by reading issues #2858 and #2882, then the proposed follow-ups #2906 and #2907, along with related issues #2698 and #1853. Clarify the supported tracker interfaces and status mappings before implementation; done means problem-list parsing can query the relevant tracker status rather than assuming GitHub issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100