If you require accessibility assistance, please send an email to firstname.lastname@example.org
JIRA is a platform that allows teams to create, capture, and organize issues, develop solutions and follow team activity for multiple projects at a time. The Office of the National Coordinator (ONC) maintains a JIRA environment as issue reporting/tracking platform that encourages user communities to collaborate on numerous Health IT projects. The system provides links to the projects, as well as other useful information relative to the topics being discussed. JIRA allows different projects to have different workflows to match current teams’ processes and the system is especially adept at capturing, prioritizing, and taking action on issues for each project. The ultimate goal for this project is to build a place where users can look for answers to questions, share suggestions, and provide real-time feedback.
To keep different project phases and milestones organized for different users in different projects, JIRA has a four-level hierarchy: Projects > Components > Issues > Subtasks.
Project – The project is the highest level container for issues in JIRA. The project level allows users to get a quick view of a project at any phase by clicking on a milestone to see outstanding issues and progress towards reaching the milestone. Reports are available on open issues, popular issues, user workloads, etc.
Component – Each project can be broken down into components (logical subsections). Users can file issues against specific components and assign component leads who are automatically assigned incoming issues. Component-specific reports are also available.
Issues – Projects are set up to track different types of issues. Depending on how the project is being used, an issue could represent a question, feedback, a form submission, a bug, etc.
Subtasks – Subtasks help break down complicated issues into manageable pieces because they are treated as separate issues. They can be defined in numerous different ways, assigned to different users, have time estimates set, etc. They can even have their own workflow that differs from parent tasks.
In JIRA, groups and roles are a way to manage collections of users. Instead of assigning a particular permission or notification to an individual users, we can use groups or roles. If a group/role is used, each member of the group/role will be given that permission or get that notification. Groups and roles are similar in their function except that groups are system-wide and roles are project specific. Also, a project administrator can manage the roles for their own project, whereas groups must be managed by a system administrator.
By default, ONC JIRA assumes three user roles: administrators, developers, and users. To better associate users and user groups with specific projects, JIRA can be further customized by adding new user roles. Groups and Roles can be used by a project’s notification scheme, permissions scheme, issue security scheme, comment visibility, and workflows.
|Administrators||Typically administer a given project|
|Developers||Typically work on issues in a given projects|
|Users||Typically log issues in a given project|
Technical support also offers Office Hours which are available Monday-Friday for JIRA users to discuss issues with an external support team: