Issue Query: Determining Important Issues

[LaraMerdol]

Prioritize issues by using some metrics such as Frequency, Recency and etc.

[LaraMerdol]

Metrics
Frequency: The frequency of comments on GitHub Issues indicates the level of involvement and interest in an issue. Issues with a high number of comments are considered more urgent and important.

Recency: Recent issues are often prioritized higher than older ones because they are seen as potentially more urgent. The recency of an issue is calculated based on the most recent data in the dataset and the last active date of the issue.

Assignees: Assignees play a crucial role in issue management on GitHub. If an issue has no assignees, it is considered to be of lower importance. Conversely, if an issue has one or more assignees, it is considered to be more important.

Milestone: Milestones represent specific goals or points in time that a development team is working towards. If an issue is associated with a milestone, it is given higher importance. Otherwise, its importance is considered to be lower.

Pull Requests: Pull requests are important for resolving issues. When an issue is connected to a pull request, it indicates that the issue requires more attention and resources. This connection helps prioritize and address issues effectively.

Labels: GitHub issues are categorized and organized using labels that indicate their category, priority, status, or other relevant features. Labels can provide insight into the importance of issues, highlighting critical or high-priority ones that require significant attention.

[LaraMerdol]

Metrics	Data Requirement
Frequency	# comment, # contributor, createdAt, closeDate
Recency	History
Assignees	Assignee
Milestone	(?)
Pull Requests	REFERENCED relation
Labels:	label