JIRA vs GitHub Issues
Open
- Dominant language
- Java
- Stars
- 154
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Description
Apache Airavata uses JIRA for issue tracking across all of the Apache Airavata repositories.
Increasingly, the project is also enabling repo-specific GitHub issues.
Clarify in this issue thread when to use JIRA vs. when to use GitHub issues.
Contributor guide
No contributing guide indexed for this repository
Research direction
The payload names no files or tests; start by reviewing this issue thread and the project's current use of JIRA and repository-specific GitHub Issues. Done means documenting a clear rule for when contributors should use each system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100