User/Groups and permissions
Users and Groups can be configured at the Site level and at the Project level. You can grant permissions defined by members of a project or members of the entire site.
This example shows that the permission to
Assign issues at the Project level can be mapped to a group named
administrators at the Site level.
Boards can be a scrum or kanban board. A Scrum board organises issues into Sprints. A Kanban board organises issues into Releases with an optional sub-filter
fixVersion in unreleasedVersions() OR fixVersion is EMPTY which basically filters extra elements out of the board on top of the existing filter for the board so as to not clutter the board.
Workflows and transitions
A project follows a Workflow Scheme which has Workflows. A Workflow has a group of statuses for Issues which can be changed via a Transition which may have transition conditions and post functions (e.g. triggering a event). A transition can also be re-used - For example, a transition named "Reopen" may be reused for the movement from Closed to Reopened and Resolved to Reopened .
Custom screens (with configurable Fields) can be assigned to
- Creating/Editing/Viewing of Issues via an Issue Type Screen Scheme
- Transitions - e.g. A resolve screen when you move transition from WIP to Resolved
You can create custom fields of certain types. For example, I've created a custom field named
Assigned Tester with a type of
User Picker and a field named
Deployed In with a type of of
Checkboxes users can tick when creating and resolving an issue.
You can query Issue's history using JQL for example
project = MyProject and status was in (Reopened) during (startofweek(), '2017/11/05 00:00')
project = MyProject AND status CHANGED FROM "WIP" TO "Resolved" BY jsmith