The XWiki project currently uses JIRA.

• JIRA Usage
• OpenProject Usage
• Requirements
  • Must Have
  • Nice to have

JIRA Usage

See JIRA Usage.

OpenProject Usage

See OpenProject Usage.

Requirements

These are the XWiki project's needs, used for selecting an issue tracker.

Must Have

• REQM01: Be able to issue queries to find issues (e.g. JQL for JIRA), including global search in all projects. It's used in lots of places, including on hundreds of pages on xwiki.org
• REQM02: Be able to label issues. We're using the following labels
• REQM03: Be able to have several resolutions for issues (Won't fix, Fixed, Duplicate, Solved By, etc.)
• REQM04: Be able to have categories (components in JIRA parlance)
• REQM05: Be able to automatically link GitHub commits with JIRA issues (i.e., links from JIRA to the commits)
• REQM06: Be able to have several issue types
• REQM07: Be able to have graphs to follow, for example, the number of bugs created vs resolved
• REQM08: Be able to have REST endpoints to create XWiki macros (e.g., the JIRA macro) or scripting in xwiki pages
• REQM09: Be able to have several projects (one for each repo)
• REQM10: Be able to have several groups (categories in JIRA parlance)
• REQM11: Be able to mass refactor issues (select issues with a query and then apply changes to all of them: add a fix version, etc.)
• REQM12: Be able to set permissions/groups/roles for authorization
• REQM13: Be publicly accessible
• REQM14: Be able to self-register and create issues
• REQM15: Be able to have shared schemes to share configs between projects (permission scheme, workflow scheme, etc.)
• REQM16: Be able to define custom fields (we use that for documentation and flickering tests for example)
• REQM17: Be able to receive notifications (individual or to a notification list)
• REQM18: Be able to import existing issues from the current issue tracker (e.g. JIRA) and not loose metadata ideally
• REQM19: Be able to move issues (and not have to close and copy issues)
• REQM20: Be able to link between issues (“depends on”, “is related to”, etc.)
• REQM21: Be able to see the detailed history of the issue
• REQM22: Be able to add attachments and display pictures/video integrations
• REQM23: Be able to have priorities, including a Blocker priority.
• REQM24: Be able to have statuses (open, in progress, closed)
• REQM25: Be able to self-register confidential issues (e.g. for security issues)
• REQM26: Be able to have different fields for different projects (e.g. some projects don't have the notion of Version)

Nice to have

• REQN01: Be able to have dashboards for releases (e.g. JIRA Dashboard)
• REQN02: Be able to see similar issues when creating new issues to avoid duplicating existing issues
• REQN03: Be able to execute scripts inside the issue tracker to query issues and perform changes
• REQN04: Be able to link issues with issues from an external bug tracker (Apache JIRA instance, etc.)
• REQN05: Be able to sponsor issues (e.g. we used to use FreedomSponsors in the past)